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!
Already subscribed? Log in!
Appendix 2: Optimistic locking
Article included in this offer
"Software technologies and System architectures"
(
227 articles
)
Updated and enriched with articles validated by our scientific committees
A set of exclusive tools to complement the resources