[fw-general] Re: problem with autoloading class definition for serialization and deserialization

2010-11-30 Thread David Muir
No, the object is still unserialized when the session is started. One way to get around it is by forcing string unserialization by doing something like: $obj = new obj; $_SESSION['obj'] = 'a not so random string'.serialize($obj); ... then to load ... $ser = unserialize(str_replace('a not so

[fw-general] Re: problem with autoloading class definition for serialization and deserialization

2010-11-29 Thread David Muir
Throwing it on a slight tangent, but maybe storing the objects in the session isn't the best solution. I've done it in the past, but have found that it's often more trouble than it's worth. I would do instead is either inject a Zend_Session_Namespace to store object data, or create a mapper

Re: [fw-general] Re: problem with autoloading class definition for serialization and deserialization

2010-11-29 Thread Hector Virgen
David, do you think implementing the SPL's Serializable interface can help with concern #3? -- Hector Virgen Sent from my Droid X On Nov 29, 2010 5:10 AM, David Muir davidkmuir+z...@gmail.comdavidkmuir%2bz...@gmail.com wrote: Throwing it on a slight tangent, but maybe storing the objects in the