hi, 2009/12/19 Peter Rundle <[email protected]>: >> Personally I would try to stop using the sessions, and store the client >> data in the cookie (assuming its not too heavy) >> your servers are then just a pool of state machines. You can yank any at >> any time with no loss of service (assuming you take it out of the load >> balancer first) > > Yes I agree, I think this is the best solution as the application has so > many queries to do on the database in any case before it presents any pages > I hardly think that the minimal data stored in the session is worth any > speed saving. Then it doesn't matter which server you hit for the "next > query".
there are trade-offs here as well - remember that cookie data goes back and forth with each request, so this gets painful very quickly. personally, i think its best to look at this case by case and use a mixture of cookies and session data. also, you'll likely want to encrypt the cookies if you want to put lots of user-data within them. cheers justin -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
