No user id to lock the db - it's not needed - if you understand threading you will know this is true.
I kind of understand threading (but I guess not well enought
). When I was doing my testing, I was able top successfully unlock a record that I had not locked. Basically I created 6 threads that would book some seats on the same flight. I think started 3 of those threads and created a new object that called the lock method directly (since it was accessable in my Data client per Sun's specification).
The new object was able to unlock a record that it had not locked. So, I ended up using the thread id (or whatever you call it) to keep track of things.
Not sure if that is the best design, but it seems to be working okay and I don't have to change the signature of the methods.
If you have any insight (or links) let me know. I've looked at threads, but I think I just need more experience using them.