With any luck, I should find some time this evening to finish and test
the code for tunneling ra_svn over an external agent. But I need to
pick a URL syntax to communicate to the client "ra_svn tunneled over
an external agent" as opposed to regular ra_svn over TCP.
I'm pretty sure I don't want to encode the external agent command in
the URL. The agent might be something like "ssh -l ghudson -o
Compression=yes" which doesn't sit nicely in a URL. So the agent will
come from an environment variable SVN_TUNNEL_AGENT (or SVN_RSH or
something else if people feel strongly), so all we need in the URL
syntax is one bit.
I've identified four options which I think I could live with:
(1) svn:ext://svn.collab.net/repos/svn/trunk
(2) svn://svn.collab.net:ext/repos/svn/trunk
(3) svn://svn.collab.net:0/repos/svn/trunk
(4) svnext://svn.collab.net/repos/svn/trunk
Options 1 and 2 break the common URL syntax (not the fundamental URL
syntax, which is just scheme:scheme-specific-part, but the "common
internet scheme syntax" syntax used for HTTP, FTP, and so on). The
first option breaks it by adding extra crud, of course, and the second
option breaks it by using a non-numeric port specification. Option 3
does not break the common URL syntax but is maybe a bit too magic.
Option 4 does not break the common URL syntax but eats a second URL
scheme, which might be considered antisocial.
I will note that RFC 1738 specifies that the common internet scheme
syntax is for "URL schemes that involve the direct use of an IP-based
protocol to a specified host on the Internet," which tunneled ra_svn
is not. (Normal ra_svn is, of course.)
Opinions?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 4 17:42:36 2002