Re: Session management module: how ASP does it

On Fri, May 28, 1999 at 08:32:45PM -0400, Steven Lawrance wrote: > > Ok, at this point, I guess we should start finding people that want to > > actively work on that project. Any volunteers? > > Hi :-). I signed up on the PHP-DEV a couple of months ago with the intent > to work on the session/application objects. Due to time constraints, I > decided to wait until the summer to work on this. Because it is now the > summer =), I have more time to actively develop this. When I spoke with > Stig Bakken March/April, one idea that seems really cool is implementing a > separate RPC server that allows PHP to store session and application data > and possibly even call PHP scripts on the RPC server. This would allow one to use multiple frontend webservers and one database-like backend RPC server. Nice idea. It fits into the model we have developed so far as a data storage container. I already have some working code which implements the basic functions (session id handling using cookies, concept for a storage modules, file based storage module, variable serializing/unserializing). It still needs some work in the configuration section and the handling of objects (classes) is also not complete. > Here is what I would like to see: > > When you want to use a session variable, you can either use the > session_variable() function or, if you're making a script from scratch, > declare variables as "session" or "application" (or "app" if > that's too > long). That could become difficult, if you think about the different contexts where such a variable identifier could be used. Up to now, we have only spoken about global variables. > If you have an RPC server that is external from the PHP module (if running > as one), then multiple web servers can access that RPC server if the > security permissions are set that way. With this, if a server goes down and > a client is automatically sent to another web server via router/gateway > magic, the PHP script on the other server can use the same variables and > data that the other server was using with that client/session. With this > capability, ASP shops might take a closer look at PHP :). Furthermore, we > should give PHP developers the option to either use session/application > objects easily (as above in my code example) or manually (as in the previous > e-mails). This actually makes it easier than ASP! And that's what we need > to win developers over.. The _only_ thing holding me back from PHP is the > lack of good session management, and with the ideas in this e-mail and the > other e-mails in the last couple of days, my ASP days will soon be over, and > many others too ;-). Well, as mentioned before, PHP already has working, enterprise-level session management in the form of PHPLIB. Your proposal increases the complexity of the session approach dramatically. In the sense of Zeev's KISS, we should start simple and extend it later. -- Regards, Sascha Schumann Consultant -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net