tomass wrote: > Hi Folks, > > I'm sure there's a better solution for this, just not sure what it > is... > > I have a 4 step form and I'm currently capturing all posted data > between each step and then re-posting it through hidden input fields > and recapturing it at each successive step. URL redirects won't quite > work for me as a better solution, since I have so much data that I > don't want to show what all of that is in the URL such as: > > /<id>/<ipaddress><ipaddress><ipaddress>/<options>/ > > for instance. > > What's the more elegant solution for this?
I actually like that solution (among other things it scales on a cluster without hammering a central db or having to distribute sessions). But if you want you could store data on the server and pass a form 'session' token as one hidden field across the pages. For really detailed forms I'd tend to use a URL as the hidden field and hold all the data captured there. If the user can go away later and re-continue where you don't just time them out on the session (ie like a grants application form) create a model for the form data and associate it with the user. cheers Bill --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
