of course I run process X only on one machine at the same time. But it
should work even if You run at the same time. But this simple case even not
work in machine A.
czw., 10 paź 2019 o 14:11 Tomasz Michalski
napisał(a):
> I have problem that despite the code is the same on both machine A an
nvoking various tools.
This is very strange I cannot connect and "invalid argument" information is
very useful:)
czw., 10 paź 2019 o 10:13 Doron Somech napisał(a):
> It is a different sockets (sock2 and mSock), therefore the ack from C will
> be received.
>
> On Thu, Oct 10, 2019
One correction:
//Send resp to machine B (not A)
mSock.send(msgAck)
}
czw., 10 paź 2019 o 09:45 Tomasz Michalski
napisał(a):
> Hi
> I have three machines. On each of them there is daemon app which perform
> role as server REP and bind to "tcp://*:". Moreover on
Hi
I have three machines. On each of them there is daemon app which perform
role as server REP and bind to "tcp://*:". Moreover on each machine
one-shoot tool can be started by user in runtime which behaves as client -
create socket on port ,
of course here is sock.bind("tcp://*:"), not udp
czw., 29 sie 2019 o 14:19 Tomasz Michalski
napisał(a):
> Hi
> I have problem with usage of zeromq.
>
> I am able to create server socket over tcp:
> zmq::context_t context(1);
> zmq::socket_t sock(
Hi
I have problem with usage of zeromq.
I am able to create server socket over tcp:
zmq::context_t context(1);
zmq::socket_t sock(context, ZMQ_REP);
try
{
sock.bind("udp://*:"); //BTW: ip address of this server is
192.168.101.1
setDefaultSocketOptions(sock,
