[eluser]theseamusjames[/eluser]
So I built this beautiful, sophisticated wizard for my company that functions by building these elegant, complex objects through a series of questions (30 of them), and now we've hit a pretty major snag.
We save that object to a session var during the construction process, then write it all to the DB at the end. Problem is, with the right combination (or wrong combination, if you're me) of options, the session object gets too large and the browser drops the cookie. It seems we're hitting that 4k limit.
What I'm wondering is, if I break up the object and use more than one "set_userdata" to save the objects, will it write them to multiple cookies and thus avert the single cookie size limit?