> -----Original Message----- > From: Tom Worster [mailto:fsb@xxxxxxxxxx] > Sent: 09 September 2009 02:29 > > thanks, Devendra, that's pretty much the same as my handler. (though > i can't > figure Rich Smith's $sess_save_path global. do you know what is > for?) I think if you look at the comments on that article, he's agreed that's an error and shouldn't be there. > but what i'm really interested in is people's experience in > switching over > to and using this kind of handler: pitfalls, gotchas, etc. or is it > really > as easy and simple as all these online articles i've read about it > claim? I moved from a single server to a load-balanced setup with 2 back-end servers. I switched to a database-based session handler very similar to the one under discussion (just tailored to my house style, really) and it just worked. Been running happily in production for about 6 months now. Cheers! Mike -- Mike Ford, Electronic Information Developer, Libraries and Learning Innovation, Leeds Metropolitan University, C507, Civic Quarter Campus, Woodhouse Lane, LEEDS, LS1 3HE, United Kingdom Email: m.ford@xxxxxxxxxxxxxx Tel: +44 113 812 4730 To view the terms under which this email is distributed, please go to http://disclaimer.leedsmet.ac.uk/email.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
