That's what Peter explains in it's previous post.
Dyndns supposes that the user already know about the server he wants
to connect to.
The idea behind zeroconf is to advertise the available svnserver to
all clients that are able to handle it.
And as Garrett says, the best thing is, not only to advertise
svnservers but also all or part of the repositories availables on
Le 22 sept. 06 à 23:37, Ionel GARDAIS a écrit :
> Forwarded for Danny van Heumen
> Début du message réexpédié :
>> De : Danny van Heumen <email@example.com>
>> Date : 22 septembre 2006 19:12:02 HAEC
>> À : Ionel GARDAIS <firstname.lastname@example.org>
>> Objet : Rép : Adding DNS-SD support to svn
>> Ionel GARDAIS wrote:
>>> But :
>>> 1/ it means these are 2 step commands which add overwork for
>>> users and hardly scriptable (because it would need a human
>>> decision of which service to use)
>>> 2/ Bonjour philosophy is to abstract the real IP of a service
>>> behind a more "explicit user friendly" name (just like plain DNS
>>> but with self server registration).
>> This sounds a lot like dynamic DNS to me. I.e. DynDNS' Static/
>> Dynamic DNS services (www.dyndns.com), which allows you to create
>> a DNS name that points to the IP of your choice. So if you want to
>> relocate the server, you would only need to change the target IP
>> address of the DynDNS account. At least one difference is that
>> DynDNS doesn't need a specific 'bjr://' prefix.
>> Could you explain the differences?
>> PS: This can ofcourse also be done with any hosting package that
>> allows you to modify your own DNS records. (Or even by adding a
>> domain in your hosts file.)
Dicouvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/Riponses pour partager vos connaissances, vos opinions et vos expiriences.
Received on Fri Sep 22 23:43:49 2006