[zeromq-dev] Fwd: ZMQ Closure - Change of Beginners Documentation
mike at kaew.be
Wed May 25 17:22:07 CEST 2011
Thanks for cutting in and ending the debate.
If its OK with you I will let you put this on zguide. My intention was only
to bring to everyones attention that the current guide is clearly wrong and
being simple I believed in it and this cost my client some money.
Martin asked me to reword the guide. This I did already.
I can assure everyone that what I wrote is a lot better than the very
inaccurate section that currently exists and I am a bit sad that my
submission ended so abruptly.
P.S. I still recommend that you don't guide people to test for ETERM as
confirmation that the system is closing down. That will be as helpful as
telling them to close all sockets before calling zmq_term.
On Wed, May 25, 2011 at 5:02 PM, Pieter Hintjens <ph at imatix.com> wrote:
> On Wed, May 25, 2011 at 4:52 PM, Mike Pearce <mike at kaew.be> wrote:
> > For information, I am not convinced that ETERM will always be the exit
> > returned. In reality It does not matter and I prefer not to test for this
> > value. My loop is of the form...
> Indeed, this works. I'm pretty sure ETERM is properly delivered but
> there may be other signals, such as EINTR if your process is killed by
> Mike, thanks for the suggestion for the Guide. I'll rewrite that text
> based on your comments and those of others. There are certain shutdown
> patterns that work. It depends somewhat on the type of threads and the
> work they are doing.
> Could you, to make sure this doesn't get lost, create an issue on the
> zguide issue tracker, and make clear what concepts you found
> confusing, badly explained, or that you assumed would work, and would
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the zeromq-dev