[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Adding a no-op LOCK to mod_dav_svn

From: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2003-01-04 12:58:10 CET

> From: Greg Stein [mailto:gstein@lyra.org]
> Sent: Saturday, January 04, 2003 12:32 PM
> To: Greg Hudson
> Cc: dev@subversion.tigris.org
> Subject: Re: Adding a no-op LOCK to mod_dav_svn
> ...
> One comment: Microsoft Office doesn't like the locks to expire on it. It
> written very poorly in this regard :-( It won't reaquire the lock, and if
> recall correctly, you can't even do a "save as" to save the document to
> local disk (presumbably cuz it tries to unlock the doc on the server, but
> fails since the lock no longer exists). Ideal operation says to avoid
> expiring locks whenever possible.
> [ well, locks *do* have a notion of expiry time; Office will refresh the
> lock "near" the expiry time; of course, it also does it "too near" and
> network latencies kill off the lock... (mod_dav gives clients a
> two minute
> margin to refresh their lock just cuz of Office) ]
> Isn't it just fun when a standard has so much variety? :-)

Actually, in this case we should blame Microsoft (for testing their clients
only with their own non-compliant servers), not WebDAV.

> ..


<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 4 12:59:21 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.