${renderedContent}
Quick Links to:
About this Page
${renderedContent}
Example Situation
To set the scene, here's a typical situation in our web applications:
- Dave pulls up data in his browser. Goes to lunch.
- Shahla pulls up same data, makes a change and saves. Changes are committed to the DB.
- Dave comes back from lunch, changes the data on his screen and saves. Changes are committed, overwriting Shahla's changes.
Obviously this isn't good; when Dave finally submits changes, we need the app to detect that someone else has changed the data, and to handle the situation appropriately. Two aspects to doing this are:
- Detection - how to detect a concurrent update
- Handling - what to do if we detect a concurrent update
We'll take these in reverse order:
Handling a Concurrent Update Situation
${renderedContent}
Detection
${renderedContent}
Chosen Solution
${renderedContent}
Further Reading
${renderedContent}