Greg Hudson wrote:
>On Mon, 2004-10-18 at 19:12, Ben Collins-Sussman wrote:
>
>
>>On Oct 18, 2004, at 6:02 PM, Branko Čibej wrote:
>>
>>
>>>I'd even consider implementing lock timeouts as something mod_dav_svn
>>>handles itself, so that the repopsitory wouldn't have to know about
>>>lock timeouts at all.
>>>
>>>
>>>
>>I don't think we should be designing locking for only one RA layer.
>>
>>
>
>I don't think that's what Branko meant,
>
No, it's not. I meant that Subversion /qua/ Subversion shouldn't support
lock timeouts. But mod_dav_svn (not ra_dav!) obviously has to.
> but I don't see how we can do
>what he says unless mod_dav_svn can somehow pop up three minutes after
>the lock request and nullify the lock.
>
>(To put it another way: if I use mod_dav_svn to request a lock which
>expires after three minutes, and then I use ra_local to attempt to
>commit to the file five minutes later, that commit needs to succeed.
>Which means either mod_dav_svn did something active three minutes after
>the lock request, or ra_local knows something about lock expiry.)
>
>
Yes, that's what worries me. One solution might be to spawn off a
monitoring process that cleans up the locks (mod_dav_svn can do that
during module initialisation).
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 19 01:29:20 2004