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

Re: Implement SRV DNS

From: John Peacock <jpeacock_at_rowman.com>
Date: 2004-04-21 19:18:15 CEST

Greg Hudson wrote:

>>OK, that's one then (and yes I was already aware of it). I also happen to
>>believe that M$loth's implementation of DNS records in this instance is an abuse
>>of the core protocol.
> And why is this an abuse of "the core protocol?"

I meant the larger issue of how Active Directory attempts to turn DNS into
something like a general purpose database protocol. The number of queries
required to resolve AD records is quite obnoxious.

There have been several studies in the media that suggest that up to 20% of all
query hits to the root nameservers are bogus, of which a lot were misplaced AD
queries. Sure, those hits all came from misconfigured clients and networks, but
it was M$loth's great implementation that is ultimately at fault.

>>In addition, the Subversion client would be required to link to a resolver
>>library to make use of this feature. Right now, the client merely requests the
>>IP address associated with a name, then opens a connection to the requested port
>>on that address. Implementing SRV would require yet another platform
>>independent library to resolve the chain of SRV records.
> SRV records don't form a chain.

Poor choice of words on my part. I meant that the Subversion client would need
to track all possible answers and try them in order (after suitable timeouts if
necessary). It is a much more complicated process than simply requesting an
address from a name and trying the connection.


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 21 19:18:16 2004

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

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