I am a new Django person as well. There is one other point about storing data in sessions. If you expect the site to grow you should put the session data in a back-end database. This will allow multiple servers to access the data. This is important if you ever want to have load balanced servers where more then one system will be tasked with rendering the next request.
For a commercial site I did we created an entirely separate database table that stored incomplete form data. The table had fields for ALL of the required final data plus a user ID key (some vital part of unique information for that person, which was entered first when they started the processes) and a last updated date field. When work was done it the last updated field was updated (even if they just logged in and reviewed their status). Then we only needed to provide a login id so they could comeback any time to continue updating. They could also go to any page or stage of the input process because the data could be gathered based on the login credentials. This kept the data out of the sessions. We also had to have a back end process which cleaned up the table of any incomplete work that hadn't been accessed in 3 months. + Leeland --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
