So how do you solve the problem of two users concurrently editing the same record?
You could do something like gMail that saves a draft of your e-mail only that your draft is your model(s) serialized. However, you still need to indicate to the user that some of the fields which have been saved in the draft have been updated. ie: You would need to restore the draft model and compare it against the life one. Perhaps you should do that on an Ajax timer event on the page that would check each 10 secs or so for changes done to the back-end? Boy, I'm glad I don't have to worry about your use-case :) Perhaps you should start a new e-mail thread specific to your use-case instead of "auto-save". On Wed, Jan 8, 2014 at 11:43 AM, gmparker2000 <greg.par...@brovada.com>wrote: > Its not so much that the user will actively be working on the form that > long. > Its more a case that users can get distracted for extended periods of time > while they are working with our form. If they half finish the data entry, > then have to take a few phone calls, it wouldn't be great if they lost > everything they were working on. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Auto-save-feature-tp4663517p4663559.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
