Gordon, Your last suggestion sounds workable but remember that the changes saved in a cookie will of course not be visible to other user, or the same user on a different computer.
As Brian said, your management are wanting the browser and form to do something that they're not designed for. I would personally put my foot down about this one, but understand that may not be an option. Is there any particular reason someone would fill out the form then navigate away from the page? My choice of solution would be submitting the changes as they are made, but with a minimum gap of 15s between each. You did say that traffic would be a problem, but unfortunately (IMHO) the management need to understand the old having cake and eating it concept :-) Good luck! --rob On 5/30/07, Scott Sauyet <[EMAIL PROTECTED]> wrote:
Gordon wrote: >>> Doing an AJAX post whenever the form changes isn't acceptible >>> because that would generate too much database traffic. One solution I used successfully for similar requirements was to do an AJAX post for each change, and store the results in the server-side session, but not make any database calls until the user submitted the form or requested a new page or until the server session timed out. I don't know what server-side tools you are using, but if you are using Java, check out DWR, which let me do that very smoothly. I haven't yet tried to put that together with JQuery, and I don't know if they'll play nicely together. Good luck, -- Scott
-- Rob Desbois Eml: [EMAIL PROTECTED] Tel: 01452 760631 Mob: 07946 705987 "There's a whale there's a whale there's a whale fish" he cried, and the whale was in full view. ...Then ooh welcome. Ahhh. Ooh mug welcome.
