For what it's worth, I have a similar concept in storing the contents of a shopping cart. I created a 'ShoppingCart' object which can hold items and their quantities, plus it adds some convenience methods like getting the list of items, the total cost, etc. I store this object in the user's session.
Storing it in a model works too, but to me seems unnecessary as it's really not persistent data, just a holding pen. I have the luxury of leaving my object in the user's session permanently. If you have lots of wizard pages you might want to build a framework around wizards. The idea being that when you 'leave' a wizard you clean up any wizard data from the session. In my Java job we do this in a base Struts Servlet. Would Middleware be a good place for this kind of approach? Perhaps using a function attribute on each view method declaring which wizard it belongs to? I'm a noob, so I don't really know... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
