[zeromq-dev] Why UDP transport is just for radio/dish?

Doron Somech somdoron at gmail.com
Wed Aug 14 19:44:12 CEST 2019

It was easier to implement it to radio/dish than pub/sub.

The reason is, multi-part messages would require a custom protocol on top
of UDP to support the multi-part. Because UDP is not reliable that means
encode all the parts into same UDP message.

Because radio/dish is single frame, the implementation is much easier,
every message is mapped to one UDP message. No special encoding.

On Wed, Aug 14, 2019, 20:32 Francesco <francesco.montorsi at gmail.com> wrote:

> Hi all,
> Out of curiosity I would like to test performances using UDP transport
> instead of TCP (my wild guess would be that zmq needs to do less
> framing/unframing work since UDP is already packet based)... But apparently
> push/pull sockets cannot use UDP transport...why?
> Thanks
> Francesco
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20190814/c391ad02/attachment.htm>

More information about the zeromq-dev mailing list