I haven't really thought this through thoroughly, but I think I would
try some like the following:
1. Create a table used specifically for storing the "auto-save" data.
2. Use a PeriodicalUpdater (something like the one used in Prototype
JavaScript library). I recommend this because you probably want to
reduce the overhead of an AJAX call every time the field is changed.
Maybe a 1 to 5 minute "auto-save" would work. It sounds like you're
trying to replicate an auto-save similar to MS Word (or as you
mentioned Google Docs).
3. Make sure you time-stamp the temporary auto-saves and associate
them with the user. Now in the case of some failure, you'll be able
to look for any unsaved documents allowing the user to have the
option of recovering from the last auto-save. Time-stamping will
allow you to create a background job to systematically clean out old
temporary auto-saves.
4. Once the "real" document is saved successfully you would then
destroy the temporary auto-saves for the user's editing session.
In any case you'll need AJAX to accomplish this. Browsers displaying
a form just sit there doing nothing until the form is submitted. So
your solution will certainly need the assistance of JavaScript (or
some other client-side code) to get the job done.
On Oct 30, 2008, at 7:52 AM, David Avendasora wrote:
I am not an AJAX expert, but...
I think the only real choice you have is to use Project Wonder and
the AJAX tools contained that it has.
http://projectwonder.blogspot.com/ is good reading to learn a bunch
about Wonder
http://webobjects.mdimension.com/wonder/ is where the actual
downloads are.
http://wiki.objectstyle.org/confluence/display/WONDER/Tutorials has
a bunch of tutorials including how to install.
Basically, you'd surround the fields you want to automatically save
to the DB with an AjaxObserveField component, then each time a
field is changed, the action would submit those values and save
them to the database.
This will make the save relatively transparent to the user.
This will completely mess with any type of validation you may have,
including required attributes and relationships, etc.
Dave
On Oct 30, 2008, at 7:21 AM, shravan kumar wrote:
Hello Group,
Thought many people already have the below described feature
integrated to their apps and whereby I would like to know best
practices and ways to achieve the below requirement:
We have a fancy need where we need to automatically save some part
of data in a form - data entered by user in text area - to
database. This save operation should not obstruct user from
continuing feeding data to form. Basically save operation should
happen seamlessly, some people call it as asynchronously.
This is something I see when using Google Docs.
Thanks in advance.
Thank You,
Shravan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%
40avendasora.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/robert.walker%
40bennettig.com
This email sent to [EMAIL PROTECTED]
Robert Walker
Bennett Technology Group
[EMAIL PROTECTED]
(770) 957-1866 790
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
