[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: Keven Ring <keven_at_mitre.org>
Date: 2004-11-10 19:48:48 CET

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?)
Probably, assuming that A.B.C isn't obtaining an IP address via DHCP, or
some other similar dynaminc mechanism.

>Also, isn't it possible to check that the domain of a particular
>machine while resolving the address of A (i.e., if machine has domain
>B.C., then all calls for A ~= A.B.C)?
I don't believe that this is a requirement at all. IIRC, (on Unix),
there is an option called "search" that can be added to your
/etc/resolv.conf file. It appears that Windows has a similar
capability, but I haven't tried it rigorously.

The purpose of this option is to define the domain search criteria when
provided with just an "A", and "A" will not resolve.

However, that being said, one could look up the IP address for "A", and
then do a reverse DNS lookup to obtain "A.B.C".

If that is done, then
1) You don't have to worry about dynamically changing IP addresses on
the server side
2) You don't have to "guess" which domain "A" resolved to.

This also allows a machine to have aliases, although that could
significantly complicate things, eg, for virtual hosts on a web server,

Sounds like a lot of sticky edge cases...

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 10 19:49:45 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.