"Any attempt to lock a resource that is already locked should cause the current thread to give up the CPU, consuming no CPU cycles until the desired resource becomes available."
Does this mean that I cannot perform any polling of the users waiting on a lock every N seconds, or can the wait timeout without the resource becoming available?
Is it acceptable to lock the entire database while operating locally, even if there are remote users already on the system, when the remote users are not holding any locks?
Can the Server already be started on the “local server” before any remote users try to log in? I didn’t think it was possible to start another process on a remote machine.
I am using List recordLockList = Collections.synchronizedList(new ArrayList)) as a thread safe was to keep my RecordLock objects (record number, user session id), a J2EE friend of mine suggested that I keep an external file and write locked records into it, which way is better, and am I allowed to even write to an external file?
Even if you could, I do agree with Darya that logically locking the entire database is not something you want to be doing - you are blocking all the other users.
Sasparilla and fresh horses for all my men! You will see to it, won't you tiny ad?
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton