> -----Original Message-----
> From: Roland Porath [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 31 January 2008 10:35 AM
> To: [email protected]
> Subject: RE: supportedlock property
>
> I agree with Julian. We do not currently make use of shared locks in our
> client. I'm just trying to understand what's going on under the bonnet.
>
>
> Thanks for the info
>
> roland
>
> -----Original Message-----
> From: Julian Reschke [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 30 January 2008 8:40 PM
> To: [email protected]
> Subject: Re: supportedlock property
>
> Angela Schreiber wrote:
> > as far as i know the JCR api only defines what
> > would be an exclusive lock in webDAV.
>
> Right.
>
> > i would probably be possible to build the shared
> > locks into the dav-layer (using the LockManager).
> > since we never had the need for share locks its
> > not supported with the simple server.
> >
> > feel free to open an enhancement request in jira.
> > i can't promise that i have time to look at it,
> > but then anybody that wants to start contributing
> > can take this as starting point.
>
> That sounds rather pointless, unless somebody has a WebDAV client that
> actually takes advantage of shared locks.
Just for the record:
Dav Explorer uses shared locks. I don't know how it actually deals with the
resulting concurrency issues and in what way it treats them differently from
exclusive locks but they are supported.
lockdiscovery =
<activelock>
<locktype>
<write></write>
</locktype>
<lockscope>
<shared></shared>
</lockscope>
<depth>infinity</depth>
<owner>
<href>asdfasdfa</href>
</owner>
<timeout>Second-85905</timeout>
<locktoken>
<href>opaquelocktoken:aa38151c9d4c1f87d077a1740aa0c288</href>
</locktoken>
</activelock>
>
> BR, Julian
>
>
>
>
>
> !DSPAM:47a109d7148228288012654!
