Re: Function caching...

Ron Chmara wrote: > a) "Session tracking app", basically a shared memory storage, which had > a uniform set of functions that tied into PHP via session functions. We already have that with the session functions and their shm interface. It does not work, because some important state such as file handles including network and database connections are not kept in userland, but in the kernel. In order to handle this properly you need > b) "DB Multiplexor app" a db connection application, that aggregated > db calls. a single process. Within a single process such kernel based ressources can be shared freely between the threads within the realm of that process. That process need not be the same process as the web server, in fact, if it isn't, it need not be running under the same UID as the web server and is independent from the execution modell of the web server. This will, as an added bonus, make safe_mode obsolete. > c) "Page cache app" Another storage app, basically a memory area where > users could pull pre-cached results from. Easily done in userland for objects, given that you have __delegate() functionality and varargs passing. Done less elegantly in userland for common functions. Kristian -- Kristian Köhntopp, NetUSE AG Siemenswall, D-24107 Kiel Tel: +49 431 386 436 00, Fax: +49 431 386 435 99 Using PHP3? See our web development library at http://phplib.netuse.de/