Re: [fw-general] Re: Conflict between Zend_Session::setSaveHandler(memcache) and session.save_handler=memcache

2008-12-12 Thread Jake McGraw
I figured it out, thanks to Ruby developers who wanted to use shared memcache sessions between Ruby and PHP: Apparently, PECL memcache for sessions stores a specially serialized string of the form: field|serialized_object;field|serialized_object; So I wrote a decode function: function decode($s

Re: [fw-general] Re: Conflict between Zend_Session::setSaveHandler(memcache) and session.save_handler=memcache

2008-12-12 Thread till
On Fri, Dec 12, 2008 at 7:30 PM, Jake McGraw wrote: > Update: > > Looks like the PECL serialize/unserialize used for storing the > $_SESSION array is different from PHP serialize/unserialize, so when > Zend app tries to read in the serialized data it doesn't understand > the serialized $_SESSION a

[fw-general] Re: Conflict between Zend_Session::setSaveHandler(memcache) and session.save_handler=memcache

2008-12-12 Thread Jake McGraw
Update: Looks like the PECL serialize/unserialize used for storing the $_SESSION array is different from PHP serialize/unserialize, so when Zend app tries to read in the serialized data it doesn't understand the serialized $_SESSION array. Anyone have experience with this? - jake On Fri, Dec 12