Currently it is only text and not binary, so even 16 is not enough. Anyway the plan is to increase it to 39 (40 including terminating zero) which will be enough for uuid.
The reason for the currently 15 chars length is that I dont want to allocate memory for the group, so the string is saved directlt ob the zmq_msg structure which is 64 bytes. Maybe as part of zeromq v5 we will increase it to 96/128 and then increase the group to 39 bytes. If you want to use binary data you most encode it to not use zero. On Mar 12, 2016 10:20, "Alex Bligh" <[email protected]> wrote: > > On 12 Mar 2016, at 01:00, Doron Somech <[email protected]> wrote: > > > During the ZeroMQ hackathon I have added the Radio/Dish pattern (thread > safe version of pubsub) and multicast support (only for Radio/Dish sockets) > to both libzmq and czmq. > > This sounds interesting > > > • Group (Radio/Dish topic) is string and currently limited to 15 > chars (might be increased in the future) > > Can I put in a bid for at least 16? 16 is the minimum required for the > binary encoding of a UUID (128 bits). > > What's the reason for a compile time limit? > > -- > Alex Bligh > > > > > _______________________________________________ > 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
