[Full | Partial] [Read | Write] [Lock | Unlock]

• Requirements

  • Matching Locks with Unlocks
  • Read & Write Locks
  • Entire Entity or Partial
  • As an Independent Action

• Suggested Implementation - A New Method

Previous slide

Next slide

Back to first slide

View graphic version

Summarizing Microsoft’s locking needs results in no less than eight different types of locks. I will be providing a full specification of those needs in the next version of the Microsoft’s HTTP Versioning and File Control Requirements Document. Never the less the basic outline of our needs is known and is detailed below.

1. Unlocks must match Locks.

2. Multiple clients should be able to take out read locks but only one client can have a write lock on any particular section of the file.

3. A token must be available to indicate “lock entire file”. Partial locks should specify byte ranges. Locks must also be able to go off the end of a file, though they must either contain or be contiguous with the end of the file.

4. It must be possible to lock and unlock files independently of any other action. A lock method seems the logical choice.