RE: lock:// protocol hacked in

But Greg - it's only syntactic sugar. The URL can be converted any way you like.

It's ra_local w/ an extra call when lock:// is used - currently converted to
file:// + David's lock file requirement.

Could just as easily be used to jumpstart an 'option' instead.

The other method that David was working on was making an entirely new layer w/
the same file access semantics as ra_local, called ra_lock. This is not that
method.

Were you objecting to the URL as well as the new access layer?

I don't know how to make this into an option. Any suggestions?

I guess I might only have avoided one half of the problem - avoiding the new
layer.

Thanks.

-- 
Shamim Islam
BA BS
Greg Hudson said:
> On Mon, 2003-11-03 at 14:45, Files wrote:
>> The included patch file contains David's locking algorithm merged in with
>> your
>> (Greg's) specific request to piggyback on ra_local.
>
> That was Ben's idea, not mine, and he has since come around to my way of
> thinking (that this should not be a new URL scheme).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org