Re: Function caching...

> * Rasmus Lerdorf wrote: > > Again, the threaded Apache 2.0 with a resource pool mechanism on a > > per-process basis and then shared across all PHP threads is a solution > > here as well. > > On one machine or over a large cluster of web servers? On one machine. Once you start talking about clustering you are back to some sort of serialization and storing things in a datastore. > How many months will go ahead when Apache 2.0 will be > a stable release for productive servers? Impossible to say at this point. It is too early. But it certainly wouldn't be any slower to become stable than writing a PHP-friendly app sever from scratch. > > I do not agree with you that PHP needs to become an application server > > like this. It should be friendly to frameworks such as Apache 2.0 that > > Why should it be this way and not -- like Kristian suggested -- in > the way of an app server? An app server would be cool. Please write one. But in the tradition of Unix, complex systems are built out of simple components. An app server that provides these features and PHP support for such an app server would be very nice. But saying that this is something that absolutely has to be part of PHP itself is not something I agree with. If PHP gets turned into such an app server and Apache 2.0 or something else comes out that provides many of these same features, then you need to figure out how to disable these things in the PHP app server if you prefer to use the support in Apache 2.0. -Rasmus