We should consider changing the API, removing lockForReading, lockForWriting, in favor of atomic read/writes.
@tpietzsch said elsewhere:
In general I would like to move to “atomic reads/writes” semantics rather then the locking semantics (which are file-system-centric, and the way we would implement atomic read/write for filesystem).
Originally posted by @bogovicj in #141
related: Investigate "Volatile" Reads for S3
Originally posted by @bogovicj in #141
related: Investigate "Volatile" Reads for S3