[zeromq-dev] 0mq socket pool vs single socket. Question on design.

[Laurent Alebarde]

I have used successfully pools of sockets when I need custom load 
balancing between clients and workers, especially when I need a sticky 
connection i.e. one client is associated to one worker for a full 
session (several messages exchange). In this use case, connecting 
several end-points to the same socket does not work.

Typical use case: proxying ZMTP mechanisms.

Laurent

Le 24/03/2014 19:03, Pieter Hintjens a écrit :
> There's no point in creating a pool of sockets. If you want to
> experiment with multiple TCP connections, you can try e.g. calling
> zmq_connect() multiple times. Please do measure the effects
> before/after.
>
> On Mon, Mar 24, 2014 at 4:32 PM, artemv zmq <artemv.zmq at gmail.com> wrote:
>> hi
>>
>> Just came to my mind. Does it make sense to create a socket pool of 0mq
>> sockets instead of single socket. For example, if traffic to remote host is
>> tense, then can the pool help me?  To help, in terms of  sending more bytes
>> and faster.  Or should I rely on single 0mq socket?
>>
>> _______________________________________________
>> 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/20140325/812b3c3e/attachment.htm>