I see. Thank you Joshua.
Yuya
On Tue, Oct 18, 2016 at 3:52 PM, Joshua Foster wrote:
> Yes, the old data still in the queue would be sent once the dealer starts
> receiving messages again.
>
> Joshua
>
>
>
> On 10/18/2016 6:08 PM, 白木 勇矢 wrote:
>
>> Thank you for your response
Yes, the old data still in the queue would be sent once the dealer
starts receiving messages again.
Joshua
On 10/18/2016 6:08 PM, 白木 勇矢 wrote:
Thank you for your response Joshua. So I cannot avoid queue drop when
sending packet from Pub to Sub or from Dealer to Router unless I
create some
Thank you for your response Joshua. So I cannot avoid queue drop when
sending packet from Pub to Sub or from Dealer to Router unless I
create some logic to solve this issue.
According to what you explained, when I call zmq_send continuously on
Router to send messages to specific Dealer, if Dealer
Lets see if I can explain it. Each socket has its own queue/buffer. This
is what is used to track how many messages. PUB/SUB uses a drop approach
when its queue gets full. If a subscriber is slow (has a full queue),
the publisher continues publishing and does not block. The slow
subscriber
Hello everyone,
I'm trying to use ZeroMQ Pub/Sub and Router/Dealer for my school
project. I have a question about reliability of these sockets.
According to the API Page(http://api.zeromq.org/), when queue reached
a high water mark and move to mute state, Dealer is going to block,
Router is going