Hi, Just wanted to throw out a question and see if anyone has solved this better than my initial approach might.. I am trying to use a web application to lock and edit a file. Since the kernel APIs requires the lock ID to be passed in to unlock a resource, I was considering just keeping a transient list of lockIds in the user's session. If I set the default lock timeout period to just under what the HTTP session timeout is set for, I can be assurred that the transient list will be in sync (relatively speaking) with the actual lock(s) held by a currently signed in user. Any thoughts on better approaches? I am assuming that there isn't some all-powerful getLocksForUser() api hidden somewhere that would help me out more here (allowing a uri -> lock ID lookup) or some other method short of brute force killing a lock.
Thanks, James
