hi Pieter,
Interface didn't change I believe. I conducted on server host (which is
VirtualBox instace) following:
iptables -I INPUT -s windows-client-ip -j DROP
and after some time re-enabled client by flushing all iptable rules:
iptables -F
That's it..
2013/12/13 Pieter Hintjens
Could you please pastebin the code so we can have a look?
--
Justin Cook
+44 7500 960 000
+1 682 738 5380
Sent from a mobile device
On 14 Dec 2013 16:11, artemv zmq artemv@gmail.com wrote:
hi Pieter,
Interface didn't change I believe. I conducted on server host (which is
VirtualBox
hi Justin,
There's no sense to paste code. Client is - DEALER. Server is ROUTER.
Inside infinite loop client sends a message and await for reply. By turn
server -- inside infinite loop receives message and sends answer back. All
socket settings -- by default. That's it.
2013/12/14 Justin
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
Good ol' pedantry.
I'll take a stab at submitting a pull request.
-Trev
On Fri, Dec 13, 2013 at 3:14 PM, Pieter Hintjens p...@imatix.com wrote:
I'll pedantically ask that we record problems rather than features.
Problem: SUB accepts multiple connects to same PUB endpoint and result
is
Thanks all for your comments. I should clarify my use case better. I am
using the lbbroker3 pattern, where the worker uses a REQ socket to connect
to a ROUTER socket on the broker. It sends I'm READY to let the broker
know that it can serve a request. After the first request, the response
serves
Hi Mohit,
I went through the same thing recently. Not only does the worker need to know
if the broker has gone, the broker also needs to know the worker has gone:
1. worker connects to broker (based on lbbroker3 example)
2. worker sends “ready” command and waits for work.
3. broker sends idle
