[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: snv URL does not use FQDN

From: Dominic Anello <danello_at_danky.com>
Date: 2004-11-10 21:13:06 CET

On 2004-11-11 02:07:50 +0800, JM Ibanez wrote:
> On Wed, 10 Nov 2004 12:35:26 -0500, Dale Worley <dworley@pingtel.com> wrote:
> > It is a good idea, but I'm not sure there is a workable method to implement
> > it. As far as I know, there isn't any standardized way to translate "A"
> > into "A.B.C", that is, to get the fully-qualified version of an abbreviated
> > machine name.
>
> Isn't it possible for the svn client to store the IP instead? (i.e. if
> A maps to IP w.x.y.z, and A.B.C maps to IP w.x.y.z, then A ~= A.B.C?)
----8<----

Unfortunately, that means you would have to do a --relocate every time
you changed the IP address of the machine.

Rather, if the host referred to on the command line did not match the
one in the WC, I would resolve both host names at run-time. If A and
A.B.C both resolved to the same IP address, you could proceed as if the
user issued the command with the WC host.

So if you have a WC based on http://A/foo/bar and the user does:
$ svn switch http:/A.B.C/foo/wux

Then svn could look and see A and A.B.C both resolve to 1.2.3.4 and then
behave as if the user issued:
$ svn switch http://A/foo/wux

That would solve the host versus FQDN issue without having to worry
about changing IP addresses.

-Dominic

  • application/pgp-signature attachment: stored
Received on Wed Nov 10 21:35:25 2004

This is an archived mail posted to the Subversion Users mailing list.