Juha Suni wrote: > I've seen programming leakage that resulted in session files of several > megabytes, causing some minor slowdowns, but still functioning 100%. > > Sessions are incredibly handy and powerful, if used correctly. I'm not > recommending dumping all your data there, but you shouldn't avoid storing > some stuff for the duration of the session. That's what they were built for. > A few megabyte session is a terrible thing -- and better architecture should be investigated. I remember doing a shopping site with an old version of squirrelcart -- the software cached all page templates in the SESSION variable?! Needless to say that when the site would see @ 70 concurrent users the I/O for the old machine was out of hand.
I like RIFE's approach of "Use What You Need", and their unconventional albeit well thought out version of session management; http://rifers.org/wiki/display/RIFE/Acceptable+session+support Storing the user's theme preference as a non expiring cookie will work fine -- providing that user is at the same computer/browser when accessing your site and not on the road drinking a fru-fru latte at Xcafe ;) Also, the original author mentioned that PHP's Sessions never expire -- on the contrary, they are cleaned [destroyed] up religiously (with a typical setting of 10-30minutes of inactivity). Cookies can also be accessed within PHP's $_COOKIE variable to, say, include alternative theme templates. ~ Brice _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
