You are totally true on these points.
Ionel
Le 22 sept. 06 à 16:37, Garrett Rooney a écrit :
> On 9/19/06, Ionel GARDAIS <igardais@yahoo.fr> wrote:
>> Sure.
>> 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).
>>
>> Say a service named "my svn server" points to 192.168.1.1 with
>> bonjour.
>> Then, a few weeks after, is moved to 192.168.1.2.
>> The bonjour name is the same.
>>
>> With your way, the user should test if the IP has changed (according
>> that he remembers the IP he used when running the first co) then run
>> a svn sw --relocate to use the new address (if any)
>>
>> With a "bjr://" URL scheme, all these steps will be hidden to the end
>> user.
>> It could be a high-level "filter" that makes all these tests
>> everytime a command is executed (still using svn:// URL scheme in the
>> 'entries' file and doing a behind-the-scene relocation) or a plain
>> connection scheme stored as-is in the 'entries' file and opening a
>> socket to the good IP at a lower level.
>>
>> Ionel
>>
>> Le 19 sept. 06 à 17:05, Garrett Rooney a écrit :
>>
>> > On 9/19/06, Ionel GARDAIS <igardais@yahoo.fr> wrote:
>> >> I'm trying to work on this on my (rare) spare time.
>> >>
>> >> I was wondering how should I implement the bonjour URL.
>> >> That is, beside of having a repository URL like "http://
>> <server>" or
>> >> "svn[+<tunnel>]://<server>", using bonjour support mean "specify a
>> >> bonjour registration name instead of a real server name"
>> >>
>> >> example :
>> >> svn co bjr:<bonjour name>
>> >>
>> >> will run a mDNS lookup for <bonjour_name> and then use the IP
>> >> associated with it for the underlying svn connection.
>> >>
>> >> I also thought about using the svn+<tunnel> syntax (like svn
>> +bjr) but
>> >> bonjour is not, strictly talking, a tunneled connection method.
>> >
>> > When I was playing with it I did it as a separate command (svn
>> browse,
>> > or svn lookup, or something like that), which would list all the
>> > repositories it could find via zeroconf. Then you just do a normal
>> > checkout based on taht info.
>
> This sounds interesting, but I'm not a big fan of inventing yet
> another URL scheme, especially not one that's not prefixed with svn,
> and that takes its name from an apple brand name for this technology
> (i.e. call it zeroconf, not bonjour, since that's the IETF name for
> it).
>
> -garrett
___________________________________________________________________________
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos expériences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 22 17:19:54 2006