Hello Friends
I understand that REST protocol allows optimistic concurrency handling. But here is a requirement for pessimistic concurrency.
This application is used by Customer Service Representatives(CSR) and they work on a dashboard of Client Requests.
Moment a CSR picks up a client request, it should not allow another CSR to pick it up.
Only solution I see is maintaining a custom table in the backend, and keeping track of who has pickedup the request and locking it.
Moment he navigates from the client request, opening it up/unlocking it for other CSRs to pick it up.
Problems can occur in cases where CSR does not navigate from the request, or if he closes the browser window. In such cases a background program can clear the locks based on how old they are.
I see that this approach can become messy and lots of bugs can hide behind this approach.
What is your opinion? Have you done anything like this? Do you think SAPUI5 is not the right choice for this scenario? Any comment is appreciated.
Thanks
Krishna