[zeromq-dev] CZMQ zgossip: RFC on new API to dump tuples

Luca Boccassi luca.boccassi at gmail.com
Sun Jan 1 23:52:38 CET 2017


Looking for comments on zgossip. A while ago this issue was opened:

With the request of a way to access the zgossip tuple database from the

All received tuples are already published to the application as a
DISCOVER message, so it should not be necessary to have an additional
API. It doesn't give access to anything that is not already received, as
far as I can see. And API messages can't be lost, they have to be read
as the inproc socket is polled (I guess it could reach HWM? But the
zgossip API channel isn't that chatty).

On the other hand, given the tuples are stored in the actor, it might
make sense to avoid duplicating the database and the efforts to de-dup
it and keep it in sync.

To test it I have implemented 2 new commands:

    * KEYS -- return number of keys followed by each key in its own
    * TUPLE key -- return value associated with requested key


But it feels a bit awkward to use (see test case), especially the keys
dump. The alternative is to simply fix the misleading docs.

I'm not 100% sold one way or the other. What does everybody think? Any
opinion on one side or the other?

Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170101/74257336/attachment.sig>

More information about the zeromq-dev mailing list