Re: Fw: [PHP-DEV] Function caching...

> Apache 2.0 is only a partial solution for multiple reasons > (like: not available, no release date, not even (obvious) > documentation on http://www.apache.de and you commit yourself > to > a single webserver - an advantage of PHP always has been > relative webserver independence). I only mentioned Apache 2.0 as one example of a framework that would provide solutions for some of the limitations you have outlined. Hopefully there will be other such frameworks that PHP can support and in a couple of years you will have a good selection of application servers to choose between. You will pick the one that best fills your needs. Perhaps one of these is written by Zend Tech. Talk to them about that. Perhaps the entire PHP dev team, or a subset thereof will decide that it is a cool project and start a PHP sub-project to create such an application server. What I don't understand is your insistence that this absolutely needs to be integrated into the PHP language itself. I completely disagree with this as it is architecturally wrong to do so. Some things may need to be changed/added to PHP to make it easier to integrate PHP into such an app server but that is something that would be identified by the authors of such an app server. > I agree with him insofar that simple things should be simple. > But in my opinion complex things still should be possible. They > should not be banned from a language or an architecture just > because they are nontrivial. No, they should be banned from a language when they are semantically and architecturally different. You are really asking to turn PHP into a standalone multi-threaded web server. This is a complete semantic and architectural change to what PHP is today and there is no reason that such a standalone multi-threaded server cannot be written completely separate from PHP and still embed PHP as its scripting language. The only worry you could have here is that the integration would not be tight enough to do some of the things you want, but that is an implementation detail that can be worked out between the two development teams. I even submit that many of the things you are asking for can be done today by using PHP's java servlet connectivity. Of course having to write components in Java would suck, but when PHP is built this way it is able to invoke classes in an out-of-process standalone multi-threaded virtual machine that is capable of all sorts of persistency. Because this would require a lot of Java work this wouldn't be an ideal solution for most PHP users, but it does show that the architecture of PHP is at the point where something like this can be done. Sure, there are some things missing, but it is these missing integration features that we should be focusing on here. We should not be deriding the PHP development team for not building such an app server, and we should especially not be criticizing the PHP dev team based on things Zend Tech may have written or said. -Rasmus