Iain, I took that approach on an app last year, and ran into several problems. You might consider just storing the stuff in the database like you would when the process is complete. It makes the programming more wizard-izable, and with sqlobject and postgresql I'm not seeing much of a performance hit.
just a thought from another ian, cheers. -ian On Nov 9, 7:43 pm, iain duncan <[EMAIL PROTECTED]> wrote: > I am wondering what the best way to store a serialized javascript object > on per session basis. In this case, the object is an associative array > of items in shopping-cartish thing built through ajax calls, and I want > to store it such that if the user browses off to a different part of the > site they can come back and their cartish thing has not been destroyed. > > In php I would have put a stringed version of the object in a table with > the session variable as the index, and then run a cron at night to kill > all the left overs. What would be the right way to do such a thing in > gears? What would be my equivalent to a php session variable for an > anonymous users session? > > Thanks > Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
