12. Appendix 2: Optimistic locking
As we saw in Principle 7 of "Data non-exclusivity", it is not possible to reserve data, even temporarily. One consequence of this principle is that data can potentially be modified by one user while another is editing it.
Suppose, for example, the user wants to change a customer's address. To do this, he performs an activity in the appropriate SF Pilot. It's highly likely that the human-machine interface for this activity will display a range of information about the customer, including the current address. Our user starts to enter the new address, but is interrupted by a phone call. Meanwhile, another user performs an activity that changes the customer's address. Our first user, who resumes his activity at the end of his telephone conversation, is unaware of the modification made by the other user and therefore risks overwriting...
Exclusive to subscribers. 97% yet to be discovered!
You do not have access to this resource.
Click here to request your free trial access!
Already subscribed? Log in!
The Ultimate Scientific and Technical Reference
This article is included in
Software technologies and System architectures
This offer includes:
Knowledge Base
Updated and enriched with articles validated by our scientific committees
Services
A set of exclusive tools to complement the resources
Practical Path
Operational and didactic, to guarantee the acquisition of transversal skills
Doc & Quiz
Interactive articles with quizzes, for constructive reading
Appendix 2: Optimistic locking