Should all locking responsibilities be controlled by the Data Base Server and all Concurrent access be controled by the NetworkProtocol?
I'm not real sure what your getting at here. First of all are you using RMI or sockets? In my implementation, concurrent access (in regards to modification) of the Data object was ultimately controlled by the remote connection object. When the client called dataAccess.modify(), the remote connection object first called lockManager.isRecordLocked(this, record) before calling data.modify(). If isRecordLocked() returned false then the remote object threw a DatabaseException. So really I suppose the LockManager and the remote object worked in concert to protect Data from concurrent modification. Hope this helps, Michael Morris
Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius - and a lot of courage - to move in the opposite direction. - Ernst F. Schumacher
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
subject: Who's responsible for locking and concurrency?
0
