Daniel Shahaf <d...@daniel.shahaf.name> writes: > Philip Martin wrote on Wed, Feb 16, 2011 at 23:13:27 +0000: >> Branko Čibej <br...@e-reka.si> writes: >> >> > In other words, use a proper crash-resistant transaction commit >> > sequence, with automatic rollback as necessary. See the sqlite docs for >> > a description of one way of doing this. :) >> >> Possibly. But that probably introduces an overhead that is entirely >> pointless in most cases. This problem can only occur with mod_dav_svn >> used through a proxy. > > Why? Does the proxy violate mod_dav_svn's contract, or do "normal" > clients not behave in that way (even though the formal contract permist > it to them)?
A "normal" client has a connection to the server for the duration of the commit, if the server process dies/restarts the client gets a read/write error on the connection and aborts the commit. I've been thinking about this overnight and I believe I need to do more investigation on the WANdisco side. -- Philip
