This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of The Little Book of Impediments (e-book only) and have Tom Perry on-line!
See this thread for details.
Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Who's responsible for locking and concurrency?

 
Ronnie Phelps
Ranch Hand
Posts: 329
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Should all locking responsibilities be controlled by the Data Base Server and all Concurrent access be controled by the NetworkProtocol?
 
Michael Morris
Ranch Hand
Posts: 3451
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ronnie,

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
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic