Win a copy of Mastering Non-Functional Requirements this week in the Design forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Which layer the locking mechanism should be implemented?  RSS feed

 
Hanna Habashy
Ranch Hand
Posts: 532
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi guys:
I want to hear you openion about which layer in the application should the locking mechanism be implemented. Should it be considered a low level operation, implemented at the data access layer. Or,should be considered as high level operation, and implemented at the control layer level.
I am interested to hear all opinions.
thanks
[ May 28, 2004: Message edited by: Hanna Habashy ]
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Posts: 12105
246
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Hanna,

You might be interested in the really long discussion we had about this in the thread "Should lock methods be callable by the client".

As you will be able to see, some of us favour having the lock method exposed right up at the client code, and others favour having it hidden at a low or mid level.

Both have their good and bad points. Take a look at some of the arguments for and against, and work out which ones make the most sense to you.

(Then document your decision, of course ).

Regards, Andrew
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!