On Sun, 2006-12-11 at 19:04 -0800, Ian Charnas wrote: > 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.
I switched tactics and now have my cart object ( which got rather complicated because of some special needs for this client ) being stored in the cherrypy session table and it will only get written to the db if they checkout. Does that make more sense? Ie controllers do: cart = session.get( 'cart', Cart() ) do their thing session['cart'] = cart Open to suggestions though! 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 -~----------~----~----~----~------~----~------~--~---
