...
- 1:A, 2:B, 3:C appear an extra time in the log (when they are masked).
- A', B', C' appear an extra time in the log (in T).
- Client clocks must be synchronized and/or other clients must always wait some amount of time before aborting a transaction
- Blind (unconditional) modifications are no longer possible as the objects they operate on may be masked.
- Having an object in the read-set of a transaction bumps its version number, so it invalidates everyone's cache.
- Can only support creates using server-assigned object IDs if it is acceptable to burn object IDs when clients crash.
- It'd be hard to do this safely if we need to consider access control. (We don't with namespaces.)
...