> Hi,
>
> first of all my thanks for your quick reply!!
>
> Remy wrote:
> REMY> Slide has read locks for properties / revision tree / content (but
not for
> REMY> the namespace structure). Since we're allowed by WebDAV to expose
additional
> REMY> lock types, we could expose read locks (but Word wouldn't use them).
>
> Christopher Lenz wrote:
> CHRIS> there is no read-locking in WebDAV. In some applications (MS Office
too, IIRC),
> CHRIS> User B will only be able to open the file in write-protected mode,
because the
> CHRIS> app tries to lock the resource when opening it. normal GET requests
are never
> CHRIS> affected by a lock though.
>
> Do you think it's possible (or sensible) to write my own WebDavServlet
> where I would include the desired locking behaviour in the GET and PUT
> Method?
Yes, that would be a good solution. We won't do it as part of Slide, since
it would be a (minor) violation of the WebDAV specification.
> this is how I would like the GET Method to work:
> - if the resource is not locked, lock it with a given timeout for this
> user
> - if the resource is locked but by the same user, allow GET
> - deny access to all other users
Yes.
> this is how the PUT method should work:
> - if the resource is locked by the same user: perform PUT and unlock
> it
> - deny access to all other users.
That behavior should be equivalent to setting the enforceLockTokens flag to
false in the SlideToken.
The problem here is that Word won't attempt to steal locks.
For example, one can use DAV Explorer to get the locks tokens of the locks
he owns, and then use the lock token to write / unlock.
> With these two changes, I can even get WinWord to work in my way,
> right?
Yes.
Remy
