[zeromq-dev] Does ZMQ handle tcp-RST?

[Bruno D. Rodrigues]

Check the new IMMEDIATE flag



--
Bruno Rodrigues
Sent from my iPhone

No dia 17/12/2013, às 08:57, artemv zmq <artemv.zmq at gmail.com> escreveu:

hello there, devs

do we have any updates here?


2013/12/14 artemv zmq <artemv.zmq at gmail.com>

> Ok.   I set HWM to 0.  Launched DEALER (my client) , and ROUTER (my
> server).  Client sends "hello" , server replies with "world".  Laucnhed
> them in separate processes, looked
> at logs, seen some chatting, hello-world-hello-world , and so on.   And
> then I decided to kill server process (on windows in cmdline:   taskkill /f
> /pid  <<PID>>).
>
> I expected that I would see the warnings produced by my application (since
> appl. logic is checking the result of .send(byte[])  function).  But
> .send()  is  always good.
> So, with HWM=0  on socket   and gotten   RST,   .send()  function  still
> tells me that send  was successfull.     Isn't this is a bug ?
>
>
> 2013/12/13 Pieter Hintjens <ph at imatix.com>
>
>> On Fri, Dec 13, 2013 at 9:14 PM, Justin Karneges <justin at affinix.com>
>> wrote:
>>
>> > If you want to prevent queuing in all cases, set HWM to 0.
>>
>> This will not actually prevent all queuing, just remove buffering in
>> ZeroMQ. You'll still get buffering in TCP and on the network itself.
>>
>> If you want to remove all queuing completely, you have to switch to a
>> synchronous REQ/REP model, which is nasty. Better, use a credit based
>> flow control system to manage precisely the total amount of buffering.
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
>
>
_______________________________________________
zeromq-dev mailing list
zeromq-dev at lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20131217/147eecd5/attachment.htm>