Making optimistic locking safe
Continuing my questions on locking, from a question I'd asked on the PDN article on Pega7 case locking...
Here's the Pega7 design: “Agents and services such as SLAs and bulk actions can update a case that is being worked by an operator. When the user attempts to save work, the update will fail.”
That doesn't sound like a good design. Is there anyway to use optimistic locking wherein a user's lock could take precedence over that of an agent process?
Moreover, this touches upon the question of whether the engine -- via a Websockets-like messenging -- can notify the client of locklost before the user clicks submit?
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Keep up to date on this post and subscribe to comments