1.0 approaches

[Martin Geisler]

Stephen Touset <stephen at touset.org> writes:

> On Feb 8, 2008, at 5:13 PM, Martin Geisler wrote:
>
>> Stephen Touset <stephen at touset.org> writes:
>>>
>>> This would cause even more confusion, given that no other URI on the
>>> planet uses it. Again, the old way isn't a "convention". It's a
>>> documented standard.
>>
>> And this standard conflicts with the standard use of SSH -- when
>> using a program like Mercurial that runs some data over a SSH
>> connection, then it would be nice if the program followed the
>> standard syntax for SSH paths (like rsync does, for example). I
>> expected Hg to behave like that too in the beginning.
>
> The fact that scp does not conform to the URI standard is not, in my
> opinion, an argument to abandon it ourselves. Especially when it's
> been mentioned before that Mercurial is using a built-in Python URI
> parsing library, which is (understandingly) incapable of dealing with
> scp-style paths.

Right, after I looked it up I too find it fine that Mercurial uses a
slash here instead of a colon. I just wanted to point out that Mercurial
does not use URIs all over anyway (like SVN with its ugly file:///bla
paths), so sticking to the standard should not be the main argument.

A better argument is that the URI syntax allows for specifying the port
number in a simple standard way, whereas the SCP paths do not because of
how the colon is used.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20080209/12103218/attachment.pgp