nonamepub
06-26-2009, 11:14 AM
Hello All,
I'm trying to find some information on how to implement the concept of "saving a rough draft" - A person has a long form to fill out, and he completes about 50% before realizing, "crap I don't have the information to complete this!" - I want to add functionality to save the work completed, and allow him to come back later. The form ties into a DB backend, FYI.
I've brainstormed a few approaches...
1. I could store the half-completed information in a session cookie. Not a great idea.
2. Create duplicate tables of all information with some "temp_" prefix. When they save a draft, I'll save it to these tables, which have NOT_NULL parameters disabled. This will increase my storage costs, and complicate my database. Not great, but easily implementable
3. Save to some XML file on the webserver.
Does anyone have any other ideas? Any links to standardized procedures?
Thanks!
I'm trying to find some information on how to implement the concept of "saving a rough draft" - A person has a long form to fill out, and he completes about 50% before realizing, "crap I don't have the information to complete this!" - I want to add functionality to save the work completed, and allow him to come back later. The form ties into a DB backend, FYI.
I've brainstormed a few approaches...
1. I could store the half-completed information in a session cookie. Not a great idea.
2. Create duplicate tables of all information with some "temp_" prefix. When they save a draft, I'll save it to these tables, which have NOT_NULL parameters disabled. This will increase my storage costs, and complicate my database. Not great, but easily implementable
3. Save to some XML file on the webserver.
Does anyone have any other ideas? Any links to standardized procedures?
Thanks!