On Thu, Feb 06, 2014 at 04:34:03PM +0100, Laurent Alebarde wrote:
Hi Devs,
I wonder please what differentiates connected peers on a ZMTP point
of view ?
To be more clear, let's consider this network:
Client 1 205.23.12.47
Server
On Fri, Feb 07, 2014 at 09:32:14AM +0100, Olaf Mandel wrote:
Am 06.02.2014 18:50, schrieb Michel Pelletier:
It's true a client can only make ~60K outgoing connections (due to
ephemeral port exhaustion) but a server with bound sockets can have up to
64K connections _per port_. Here's a blog
On Fri, Feb 07, 2014 at 06:09:40PM +0100, Benjamin Cordes wrote:
Maybe a simple publisher on two channels is enough? i.e. in pyzmq the
following you did not provide much information
# simple publisher
import zmq
from random import randrange
import random
import time
import json
On Sun, Feb 09, 2014 at 12:16:48AM +0100, Laurent Alebarde wrote:
When I replace the tcp address tcp://127.0.0.1:5556 with an
*inproc* one, say inproc://testStream, in /tests/test_stream.cpp/,
the test fails. It asserts on
rc = zmq_recv (stream, buffer, 255, 0);
assert (rc == 0);
Le 10/02/2014 10:43, Goswin von Brederlow a écrit :
On Thu, Feb 06, 2014 at 04:34:03PM +0100, Laurent Alebarde wrote:
Hi Devs,
I wonder please what differentiates connected peers on a ZMTP point
of view ?
To be more clear, let's consider this network:
Client 1 205.23.12.47
Le 10/02/2014 11:12, Goswin von Brederlow a écrit :
On Sun, Feb 09, 2014 at 12:16:48AM +0100, Laurent Alebarde wrote:
When I replace the tcp address tcp://127.0.0.1:5556 with an
*inproc* one, say inproc://testStream, in /tests/test_stream.cpp/,
the test fails. It asserts on
rc = zmq_recv
As far as I can tell from reading all of the documentation I can find,
by default when you use a PUSH/PULL socket and don't mess with the
LINGER socket option, when you terminate your 0MQ context at the PUSH
end, it should hang until all the messages have been successfully
delivered to the
Hi ZeroMQ experts,
I am investigating how one might add SOCKS proxy support to 0mq, and of course
there are several options. But I was thinking that the most elegant would be to
add support for a socks protocol to 0mq. I took a look at the source code,
and I was a bit surprised to find that the
