Atomic locking of a collection (cont’d)
Pro:
- prevents situation where more than one autor try to lock a set of resources simultaneously, and all end up with some, but not all the locks they want.
Con:
- it is difficult to implement atomic locking behavior within a server (appears to require transaction support)
- a LOCK method can only specify a single URI, so this would have to be satisfied with a collection of external member resources