Hi Erickt,

> I also finally cleared my example with work, and you can find it here:
> 
> http://github.com/erickt/bonjour-forwarder
> 
> It currently just reflects browsing bonjour to zeromq.

        Looks like a nice start.  Just a couple thoughts though:

1.      With the auto resolution the messages are going to be massively
spammy in a large scale system.  Just an example, for 40k our services were
each defined as: "_<service type>_<shard hash>._tcp".  So, with 8-9
development branches going there were about 400-500 services running at any
time.  Resolutions can be very time consuming.

2.      From what I can see this lacks any type of record query?  Just
curious as that is one of my primary needs from zero conf.

3.      This is likely to be very touchy to startup order is it not?  I.e.
if the guy that wants to know about a service takes a little longer to start
than normal it will miss the registration message won't it?

        Anyway, good start for something if you just need to know where to
find things.

KB

> On Mon, Sep 20, 2010 at 1:34 AM, Gaspard Bucher <[email protected]> wrote:
> > I also moved the code from oscit in http://github.com/rubyk/zconf (a
> simple
> > wrapper for ZeroConf and Avahi).
> > We will see what proves best, wrappers around mdns or a custom made
> service
> > discovery on top of ZeroMQ + openPGM...
> > G.
> >
> > On Mon, Sep 20, 2010 at 1:27 AM, Kelly Brock <[email protected]> wrote:
> >>
> >> Hi folks,
> >>
> >> > >        Actually, the latest Bonjour distro's for Win32 and OsX both
> >> > > directly include easy Wan setup.  Just add the external domain to
> your
> >> > prefs
> >> > > page and it simply works.  I use this when I work from home and
> just
> >> > link my
> >> > > local boxes to my work domain so I can get services started locally
> >> > which I
> >> > > can then debug against but still using the full production
> >> > > environment.
> >> >   It
> >> > > used to be a real pain as you mention, but they seem to have fixed
> it
> >> > up.
> >> >
> >> > That is great news, I haven't looked at this stuff for a while.
> >> >
> >> > >> For zeromq based apps and servers, it would be quite nice to have
> a
> >> > >> zeromq based naming service and I have often though about writing
> one
> >> > >> myself.  But, because of the security issues, such a naming
> service
> >> > >> won't be as useful on the WAN quite yet.
> >> > >>
> >> > >> In summary, on the LAN both zeroconf and a zeromq based naming
> >> > >> service
> >> > >> both make good sense.  On the WAN, neither do right now.
> >> > >
> >> > >        At this point I'll just say that ZeroConf, once you have a
> >> > > decent
> >> > > wrapper, is still my favorite solution.  No futzing around, it just
> >> > tends to
> >> > > work.
> >> >
> >> > Yep.
> >>
> >>        Just as a note, I threw up a very quick extraction of my
> zeroconf
> >> wrapper on github at: http://github.com/All8Up/zeroconf.  This is
> >> currently
> >> just the interfaces converted to not use my hobby framework which
> includes
> >> a
> >> lot of dependencies which would be undesirable.  (Currently lacking in
> the
> >> records interface, I want to redo that part.)  Obviously it is useless
> at
> >> this stage but I wanted to see what folks thought about this interface
> >> instead of a custom rewrite.
> >>
> >>        Raid the select poller from Zmq and it can be functional on
> >> Win32/BSD/OsX in probably a matter of hours; it would even work on
> Linux
> >> if
> >> you install the bonjour mdns daemon which I "believe" functions side by
> >> side
> >> with Avahi.  It is easily wrapped up in a C interface so it can be used
> >> pretty much anywhere.
> >>
> >>        Anyway, it's a starting point thought instead of trying to write
> a
> >> reimplementation of something which works perfectly well and is fairly
> >> well
> >> supported.  Avahi support is the real trick as I mentioned previously,
> but
> >> it's not that much work.
> >>
> >> KB
> >>
> >>
> >> _______________________________________________
> >> zeromq-dev mailing list
> >> [email protected]
> >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> >
> >
> > _______________________________________________
> > zeromq-dev mailing list
> > [email protected]
> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> >
> >
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to