Re: DATABASE SESSION vs NON DB SESSION

The question, I though, was 'why use a database, why not just use the filesystem?'. I was replying to that when I said that it (the filesystem approach) doesn't work in a multiserver setup. James Atkinson wrote: > On Fri, 13 Oct 2000, Michael Kimsal wrote: > > Jingle Balls wrote: > > > > > I have been reading the posts and some articles about PHP sessions and I got > > > myself confused (I know it happens a lot). However I am a bit perplexed over > > > this. I hear a lot of people wanting to keep session information in a DB, > > > doesnt PHP have a great server side storage of session variables? All you > > > need to keep client side is a single cookie of the sessionid? > > > > > > If this is the case, why go the DB route? You can keep preferences and log > > > info to the actual database, adn read those in when the user logs in and > > > then keep them as session variables. > > > > > > > This doesn't work in a multi-server environment - 5 web servers to > > one database server, for example. > > Umm...perhaps I'm missing something here buy why wouldn't it work? If all the > webservers access the same DB server then they all have access to the same > session information. The only problems I can see is load on the DB server.. -- ========================== Michael Kimsal http://www.tapinternet.com 734-480-9961