[zeromq-dev] question about zbeacon
ph at imatix.com
Thu Aug 7 10:57:23 CEST 2014
The original use case for Zyre (and hence zbeacon) was WiFi
clustering. However it's evolved to choosing a "best" interface
including LAN. There is little point in broadcasting on multiple
interfaces, as you cannot create a connected cluster except on a
single infrastructure. zbeacon allows the interface to be set by force
Multicast is neat (and we used to work with that) except for some
issues with Android, perhaps now resolved. I'd like to switch zbeacon
to multicast or at least support that as an option. It's also
necessary for IPv6 work.
It's very nice to see a parallel implementation in Erlang and perhaps
we can codify the discovery protocols separately from ZRE, which
they're now embedded in.
On Thu, Aug 7, 2014 at 9:55 AM, Benoit Chesneau <bchesneau at gmail.com> wrote:
> To update this thread, i've started an implementation under MPLv2 there:
> For now it is broadcasting to all interfaces where broadcast is available. I
> wonder what is the rational in choosing only the wifi interface? Also any
> idea how to make sure we choose this one?
> Like zbeacon it is only broadcasting on ipv4 and there is no multicast but I
> plan to add it soon.
> Any feedback is welcome,
> - benoit
> On Fri, Aug 1, 2014 at 8:23 AM, Benoit Chesneau <bchesneau at gmail.com> wrote:
>> On Wed, Jul 30, 2014 at 1:54 PM, Pieter Hintjens <ph at imatix.com> wrote:
>>> Hi Benoit,
>>> zbeacon does not impose any frame format; it allows the caller to
>>> specify the format for beacons. Zyre does this according to the ZRE v2
>>> spec at RFC 36.
>> oh, maybe i misread the C code. I thought it was encoding message when
>> using zmsg.
>>> So you could implement this in two layers as we do in C, one generic
>>> UDP pub/sub beacon class, and then on top of that, the details of RFC
>>> 36. Or you could do that all in a single class. zbeacon has been
>>> useful for other apps, which is why we made that a generic reusable
>> Cool! Thanks for your answer. Will work on something over the week-end
>> then :)
>> - benoit
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
More information about the zeromq-dev