* zhelpers.dump(msg_or_socket) accepts multipart message *or* sockets, so that it matches the zmsg_dump behavior as well. * add zpipe for zthread_fork-style creation of a pair of inproc PAIRs, for communicating across threads. * My previous change to zhelpers.dump was imprecise, only hexlifying if characters were outside ascii, when it should have also protected against the low-end, which is still within ascii.
…for guide chapter 3
* a comment says 0/1/2 seconds, but randof(2) only does 0/1 * zguide says client doesn't print, it sends to monitor, but code didn't actually do this. Now it does. The actual behavior of the program is unchanged, other than printing is better behaved, as it is now all done in the main thread, rather than 10 client threads.
There was a comment suggesting that the bindings swallowed an empty frame. This was incorrect, the empty frame was not sent in the first place.