[zeromq-dev] Explicit control over socket buffers?

Dmitry Antipov antipov at dev.rtsoft.ru
Mon Jun 9 09:24:58 CEST 2014


why 0mq doesn't offer the facilities to control socket buffers (except
setting send/receive watermarks and default socket policy to discard/block)?
In particular, someone can ask about functions like 1) zmq_peek, to tell
how many messages are buffered for input/output, and 2) zmq_discard, to
discard all queued messages.

It's quite possible that such a questions just illustrates some misunderstanding
about what 0mq sockets are and how they should be used; but can someone explain
the (obviously by-design) solution to _not_ provide these features?

Thanks in advance,

More information about the zeromq-dev mailing list