Brad Lafountain wrote: > I was wondering if anyone has ever thought of comming up with a different way > of handling the code below. I know that you can use shared memory, but that > wont work for win and it wont work for web cluseters using db's to handle their > sessions. Also sessions will automatically handle locking of the session info. > so you don't need to worry about using shm locking the shm.
Basically you need application level sesssion variable (or application scope persistent variable), right? SRM and session_pgsql supports that. In case of session_pgsql, $_APP can be used just like $_SESSION. All session that has the same session name shares $_APP. (SRM has OO approch for this) Supporting $_APP is easy, if nobody objects I'll add it to files handler or change session module so that all save handler can support $_APP easily. Any comments? -- Yasuo Ohgaki -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
