Re: Adding LAN support to Subversion - Clarification

Blocking mode connections are synchronous.

Non-blocking mode connections are asynchronous.

If we establish that the default subversion protocol is non-blocking, it would
suggest that it was asynchronous in that it does not hold up other requests
from being processed.

Thus a locking/blocking protocol would be by analogy, a synchronous protocol.

Using that logic, what do you all think about:

sync+file://.... for the blocking lock file protected file protocol?

Where the assumption is that the normal file://... is a tacit async+file://....

I don't know whether it would be useful to accept an async+file:// schema -
personally, I doubt it.

YMMV

-- 
Shamim Islam
BA BS
Benjamin Pflugmann said:
> Hi.
>
> On Tue 2003-10-28 at 14:57:01 -0500, Files wrote:
>> I know lock sounds strange but it does indicate what the protocol does. But
>> inherently it *is* still a file protocol.
>
> Well, IIRC, for svn over SSH we have "svn+ssh://". So how about
> "file+lock://" or "file+serial://" in order to say that is the file
> protocol "with locking" resp. "not parallel"? Well, you get the idea,
> maybe someone can come up with an expression that better says that
> concurrent accesses will be blocked.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org