10 Jan
2019
10 Jan
'19
12:36 a.m.
On 9 Jan 2019, at 20:48, Christian Grün wrote:
Are you saying that a write transaction blocks pending READ requests
until the transaction has been committed?
No. What I was trying to say is that we deliberately designed REST requests to be atomic transactions. If you perform multiple updates in a single REST operation, you can be sure that a concurrent read operation will see the state before or after the first operation, but no state in-between.
This is not true. A long running REST operation (executing a bunch of ADD and STORE commands) blocks parallel reads. A long running REST operation as in my case has serious impact on reading operations in parallel over WebDAV…the WebDAV connection timed out in my case.
Andreas