ROUTER socket doesn't set RCVMORE on identity frame
Description
Environment
None
Activity
Show:
PieterP July 21, 2011 at 12:35 PM
Patch applied to 3.0.x
PieterP July 18, 2011 at 4:52 PM
Test case was bad, tried to getsockopt of 'socket' instead of 'pipeout'. The patch at https://gist.github.com/1089590 fixes the problem.
PieterP July 18, 2011 at 11:18 AM
Affects libzmq master as well, which is expected since 3.0.0 is just a few days old snapshot of that.
When receiving the identity frame from a ROUTER socket, the RCVMORE value is zero, not 1. This breaks code which reads multi-part messages in single operations, e.g. CZMQ's zmsg class. Test case is here: https://github.com/zeromq/issues/tree/master/232