Not really, only if you are in the middle of receiving multipart
message you will continue to get it. If not, you won't get any pending
messages.
On Fri, Oct 21, 2016 at 1:23 PM, zmqdev wrote:
> Hi Doron,
>
> I tried out your latest repo
>
>
> https://github.com/somdoron/libzmq/commit/3775d0853a8c1f1c3854a94c7fe12e78046faeca
>
> with the changes to src/socket_base.cpp, src/pipe.cpp and src/pipe.hpp.
>
> I confirm that the problem reported at
>
> https://github.com/zeromq/libzmq/issues/2163
>
> is solved: the assertion in src/fq.cpp:118 is not triggered anymore.
>
> Thanks!
>
> There is one point I'm unsure about. The documentation of zmq_disconnect
> states
>
> Any outstanding messages physically received from the network but
> not
> yet received by the application with _zmq_recv()_ shall be
> discarded.
>
> https://github.com/zeromq/libzmq/blob/master/doc/zmq_disconnect.txt#L19-L20
>
> In the PUB->SUB test case, the message is not discarded by the
> zmq_disconnect, and is received (sans abort) with zmq_msg_recv.
>
> Doesn't this behavior contradict the doc?
>
> ___
> zeromq-dev mailing list
> zeromq-dev@lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
