[zeromq-dev] zmq_close() semantics and handling outstanding messages
Andrew Hume
andrew at research.att.com
Thu Jul 8 15:59:45 CEST 2010
opening and closing lots of sockets is arguably bad. agreed.
not being able to close off a communication channel with
deterministic semantics is bad.
i don't understand the difficulty of being able to ask the publisher,
that is someone who has done zmq_send's, if all those sends have been
sent.
On Jul 8, 2010, at 8:58 AM, Chuck Remes wrote:
>
> Flushing messages from closing sockets (or terminated contexts) is
> only interesting at the final stage of an application's lifecycle.
> Earlier in this thread someone mentioned that it's probably a buggy
> "pattern" if one is opening and closing lots of sockets during a
> program's lifetime. I agree.
>
> cr
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
------------------
Andrew Hume (best -> Telework) +1 732-886-1886
andrew at research.att.com (Work) +1 973-360-8651
AT&T Labs - Research; member of USENIX and LOPSA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20100708/ad65ee89/attachment.htm>
More information about the zeromq-dev
mailing list