Re: Session management module - thoughts

You can always fall through to PHPlib. Session management, ASP-style, that is, using cookies, fits most people. One of the biggest sites in the world considers it ok not to let you in most parts of the web site in case you don't have cookies enabled. As long as you tell people that they can't access the site without using a cookie-enabled browser (as opposed as just letting them use a broken site), it's fine. Zeev On Fri, 28 May 1999, Phil Glatz wrote: > At 09:54 AM 5/28/99 , Jim Winstead wrote: > >One problem is keeping track of the session key, though. Relying on > >cookies is only okay if you're willing to let people slip through > >the cracks. > > More than that, in the "real world", lots of people don't accept cookies > for various reason (older browsers, paranoia). > > I'm working on a very large ecommerce site. One of our directives to reach > a maximum office is to allow cookies and javascript as a convenience, but > do not require their use for the site to work. As much as I like them, we > cannot assume all users will have them enabled. > > I like the use of authentication, but there is no way currently to do this > on our site (at least until a mod_auth_oracle comes along). > > I'm of the opinion that session management is probably best implemented > outside core PHP, possibly as a series of class libraries. I don't see how > one general implementation will be usable by all. > > > > -- > 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 > > -- ----------------------------------------------------- Zeev Suraski <zeev@zend.com> For a PGP public key, finger bourbon@netvision.net.il -- 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