This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
we need to implement an edit lock on some of our records so that they can't be simultaneously edited by two users. Also we need to clean up the lock when the user time out happens. We thought of implementing this using an HTTPSessionListener but the servlet 2.3 API suggests that the sessionDestroyed() is called after the session is destroyed. Then we have no way to decide what and which user to cleanup?? Looks like writing our own deamon thread is only possibility Any thoughts on this will be helpful
You might be better off having an object in the session that holds the record information AND implements HttpSessionBindingListener. That way you are guaranteed that the object will get a valueUnbound call when the session is destroyed. Bill