It seems to be that what we're looking for is a simple wrapper around sysvshm or shmop (we want win32 support?) that would create $_APP superglobal and store data within that superglobal. The only issue would be that shm segment cannot be easily resized and on many systems there is an upper limit on the shm segment size. Which means you'd probably need to use a file backed shm implementation such as anonymous mmap. This however means that you cannot use shmop or sysvshm, however something like mmcache previously mentioned should be a fine solution. All you'd need to do is make a wrapper around $_SESSION.
Ilia On August 7, 2003 10:17 am, Davey wrote: > Wojtek Meler wrote: > > Davey wrote: > >> MMCache can be used as a session handler, but this still has the > >> pitfalls of the other solutions. > >> > >> If you were to implement $_APP(LICATION) as suggested, then it could > >> indeed (in theory) use MMCache, just as $_SESSION does > >> > >> - Davey > > > > As far as I understand you just want to have another superglobal > > variable, don't you? > > If so I have small patch witch allow to configure in php.ini names for > > additional superglobals. > > > > Regards, > > Wojtek > > Well, whilst this could work, it means that $_APP(LICATION) would not > have the same infrastrcture below it as $_SESSION does (automatic > serializing/unserializing and the ability to switch the data storage > from files, to user, to SQLite and to MMCache) > > - Davey > > P.S. > > Would mind that patch anyways, sounds good, just doesn't fulfill my > needs/desires for $_APP(LICATION) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
