d.Implicit Lock Pattern

  1. Motivation
    1. Allows framework or layer supertype code to acquire offline locks.
  2. Summary
    1. Implementing Implicit Lock is a matter of factoring your code such that any locking mechanics that absolutely cannot be skipped can be carried out by your application framework. 
    2. For lack of a better word we'll use "framework" to mean a combination of Layer Supertypes , framework classes, and any other "plumbing" code.
    3. Code generation tools are another avenue to enforce proper locking. I realize this is by no means a ground-breaking idea.
    4. This pattern is well supported by most of enterprise level data access frameworks.
  3. When to Use
    1. Implicit Lock should be used in all but the simplest of applications that have no concept of framework.
  4. References
    1. http://martinfowler.com/eaaCatalog/implicitLock.html