On Tue, 2007-12-11 at 15:25 +0000, Stut wrote: > Richard Heyes wrote: > >> Because it's not user data, it's server data. > > > > So? It's there - use it. > > So are cookies, would you stuff this into a cookie? No, because that's > not what cookies are there for. > > "Because it's there" is never a good reason to do something. > > >>>> That's entirely the wrong place to > >>>> store something like which database API is installed. > >>> > >>> Not really. You could even wrap a function called (for example) > >>> Feature() around it. > >> > >> Yeah, really. Sessions are for user data. If it's the same for all > >> users then it doesn't belong in the session, it belongs in a > >> server-wide cache. > > > > > > Sessions are for whatever you choose to put in them. And why implement a > > cache when you've got something perfectly usable (sessions) already?
Suuuuuuuure, sessions are for whatever you choose to put in them. That's like saying bodies are for whatever a crazed murderer chooses to put in them... the statement is true, but it's not optimal. Cheers, Rob. -- ........................................................... SwarmBuy.com - http://www.swarmbuy.com Leveraging the buying power of the masses! ........................................................... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
