Re: auto-version and shared write-locks

This is a multipart message in MIME format.
--=_alternative 0051A1E88525723D_=
Content-Type: text/plain; charset="US-ASCII"

I'd probably wait until the VCR becomes completely write-lock free.
But one could make a reasonable argument either way.
Note: I've never been a fan of shared locks, so whatever you want to do 
there is fine with me (:-).

Cheers,
Geoff

[email protected] wrote on 12/05/2006 11:37:37 PM:

> 
> >The VCR should auto-checkin when all write locks have been removed.
> 
> Do you mean all write locks present in the request that caused the
> auto-checkout? Or should we wait till the VCR becomes completely
> write-lock free (i.e, till all shared write locks of other users are
> also removed )?  I would think that a new version of a resource is
> ready when all the members who are collaborating on work on that
> resource are done and remove their shared lock. Unless this technique
> is meant to be used as a backup mechanism for individual changes made
> by users collaborating on the resource through shared locks.
> 
> Chetan
> 
> 

--=_alternative 0051A1E88525723D_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>I'd probably wait until the VCR becomes completely
write-lock free.</font></tt>
<br><tt><font size=2>But one could make a reasonable argument either way.</font></tt>
<br><tt><font size=2>Note: I've never been a fan of shared locks, so whatever
you want to do there is fine with me (:-).</font></tt>
<br>
<br><tt><font size=2>Cheers,</font></tt>
<br><tt><font size=2>Geoff</font></tt>
<br>
<br><tt><font size=2>[email protected] wrote on 12/05/2006
11:37:37 PM:<br>
<br>
&gt; <br>
&gt; &gt;The VCR should auto-checkin when all write locks have been removed.<br>
&gt; <br>
&gt; Do you mean all write locks present in the request that caused the<br>
&gt; auto-checkout? Or should we wait till the VCR becomes completely<br>
&gt; write-lock free (i.e, till all shared write locks of other users are<br>
&gt; also removed )? &nbsp;I would think that a new version of a resource
is<br>
&gt; ready when all the members who are collaborating on work on that<br>
&gt; resource are done and remove their shared lock. Unless this technique<br>
&gt; is meant to be used as a backup mechanism for individual changes made<br>
&gt; by users collaborating on the resource through shared locks.<br>
&gt; <br>
&gt; Chetan<br>
&gt; <br>
&gt; <br>
</font></tt>
--=_alternative 0051A1E88525723D_=--