Your current approach makes sense. If you're concerned that you're storing too much data in the session, you could just maintain a session ID in the session and use that as a key for an sqlite3 database or something, or even a model in your app's database, if that makes sense. Is there any reason you're unsatisfied with the way you're doing it?
Shawn --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
