[Typo3-dev] Typo3 Application Server
Robert Lemke
robert at typo3.org
Tue Jan 25 10:38:23 CET 2005
Hi Bernhard,
I have thought about this kind of thing a lot and, so far, concluded
that TYPO3 is the RIGHT thing.
On the snowboard tour I talked with some people about the idea of creating
an application server for TYPO3. The discussion also went so far that we
asked ourselves if TYPO3 should be coded in PHP in the future.
Some of our conclusions were:
- The bottleneck is NOT PHP. PHP is actually quite fast.
- Writing a deamon in PHP is no problem. You don't need a cron job nor
do you have to cheat with timeouts, you can just program a proper
daemon with forking and such like you can do in perl for example.
- One of TYPO3s bottlenecks is possibly its statelessness. Take the
frontend user sessions as an example: At each page hit we have to
query the database for getting the FE session and also write it
back at some point. If we had a daemon which held that information
for a certain time in memory, we don't have to have so many DB /
file accesses.
All that would require some event based archtitecture in the core of TYPO3.
I talked a lot with René about it and we are very confident that we will
put that into practise. It will also open new doors for controling TYPO3
remotely via SOAP et al.
Anyways, what I would like to say is: I'm totally in favour of checking out
the pros and cons of a PHP based TYPO3 application server, so just go
ahead, I'll support it in the best way I can.
--
robert
More information about the TYPO3-dev
mailing list