Because it's not user data, it's server data.
So? It's there - use it.
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?
--
Richard Heyes
http://www.websupportsolutions.co.uk
Knowledge Base and HelpDesk software
that can cut the cost of online support
** NOW OFFERING FREE ACCOUNTS TO CHARITIES AND NON-PROFITS **