On Sat, Feb 23, 2013 at 3:38 AM, Pieter Hintjens <[email protected]> wrote:
> On Sat, Feb 23, 2013 at 11:56 AM, Bjorn Reese <[email protected]> > wrote: > > ZRE does this in the HELLO message of a new connection (key/value > pairs), which is simple and optimal. Enlarging beacons is a mistake > IMO. It's especially bad on WiFi where every byte you send has a cost. > I agree, I wouldn't want to see a full complex beacons with meta data. Once bootstrapped any protocol (as you pointed out with JOIN) can exchange whatever it wants. > However I've moved the code itself into CZMQ: > http://czmq.zeromq.org/manual:zbeacon so its easy to build your own > discovery protocols with whatever you like in the beacons. Thanks for zbeacon Pieter, it largely addresses all my use cases, so it seems like changing spec 20 now isn't needed. ZRE can continue to be what it is, I can easily listen for ZRE beacons and speak it's protocol when I want to, and use zbeacon to accomplish my other goals. I do still think a little more service socket info in the beacon would be generally useful, but it's not a blocker on me anymore now that I can use zbeacon. -Michel
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
