Over in the 'Locking UI comments', Julian R. and I had a conversation about
Microsoft Office's WebDAV LOCK support and some bugs in it. There's a
development in here that now needs to be explicitly considered, so I'm
splitting this out into a new thread.
Here's the latest of what Julian said in case you missed it:
--On Thursday, October 14, 2004 7:25 PM +0200 Julian Reschke
<julian.reschke@gmx.de> wrote:
> OK, I just checked with Office 2003; it attempts a LOCK with 180s timeout;
> if the request suceeds but the timeout sent back by the server isn't what it
> expects, it gives up and opens the document read-only. Furthermore, it
> doesn't UNLOCK the document when it's closed. (Yes, that is a bug in Office;
> clients MUST NOT rely on servers supporting specific timeout values, see
> <http://greenbytes.de/tech/webdav/rfc2518.html#HEADER_Timeout>).
>
> So it seems that adding locking functionality without timeout support will
> not help for the MS-Office use case.
So, if we don't support timeouts, Office/Word will refuse to play ball. And,
part of my ideal for LOCKing is to get Office users happy. However, it
changes some parts of our locking UI (some significantly). So, first, before
going down that road, is it important enough to support locking with Office
and a Subversion server that we add timeouts?
Yet, this is going to introduce a whole set of goofiness: locks may not
necessarily have to be 'unlocked' - they can just expire. Ideally, we'd go
for a lazy expiration model. And, lots of other things need to be thought
about timeouts as well from a user perspective.
What do the rest of ya'll think? -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 15 07:08:27 2004