Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Rather than using a ‘save’ button on a web form, many web designers like a ‘save as you go’ approach. Where as the user’s changes to the data are saved immediately once the user changes focus out of say a text box.
Has anyone identified a formal pattern for this technique? I especially need to tie it all back to chunky service call. Concurrency issues seem to be one of the first issues coming to mind.
Ajax Patters has the Object Persistence pattern which sounds like what you’re describing.
You may also want to look at the Fat Client article regarding response issues which might arrise.