Author Archives: Thomas Howe

Locking Users Out of a Web Process

I had a client that wanted to only allow one user to maintain an order record at any given time. When a user is in an order we will set a field to the user that is using the order so we can tell anybody being locked out who currently has the lock. For some applications it is fine to simply set this lock in one location where the user enters the order and unset the lock in another location when finishing the order. Similarly to WebSmart’s Change Management, we know this can often result in orphaned locks over time if the browser is ended abnormally. In this case even the simple act of the user closing the browser will not trigger the unlock.

Continue reading