[zeromq-dev] zeromq DEALER client to multiple servers (ROUTER)

ashish nagar ashish_nagarudr at yahoo.com
Mon Sep 30 05:57:13 CEST 2013

Thanks for the feedback. 

In case I can't use the router broker socket approach in my use case, what do you think about creating multiple DEALER sockets on client side  - one for each server endpoint (ROUTER socket)?  Is it recommended by zeromq best practices?

In my use case, client has list of server endpoints and client selects server before sending the message. 



 From: crocket <crockabiscuit at gmail.com>
To: ashish nagar <ashish_nagarudr at yahoo.com>; ZeroMQ development list <zeromq-dev at lists.zeromq.org> 
Sent: Monday, September 30, 2013 1:59 AM
Subject: Re: [zeromq-dev] zeromq DEALER client to multiple servers (ROUTER)

a ROUTER socket on the client can connect to multiple ROUTER sockets on servers.

Such a client ROUTER socket can choose a specific ROUTER socket to send its messages to.

On Sun, Sep 29, 2013 at 3:25 AM, ashish nagar <ashish_nagarudr at yahoo.com> wrote:

I am using ZEROMQ for distributed messaging application. Need to connect client (DEALER socket) to multiple servers (ROUTER socket on server side).  What are my options on CLIENT side ?
>	1. Create DEALER socket on client side for each server endpoint (ROUTER socket). 
>	2. Create only ONE DEALER socket on client side and add multiple endpoints. 
>I tried option 2 -  connecting to multiple endpoints but message 
always goes to the first connected endpoint. followed following steps:  - create  DEALER socket - connect to first endpoint  - then on the run time,  add another endpoint to the socket by using 
socket.connect(endpoint). Do I need to reconnect?
>In DEALER socket, there is no option to send message on a particular endpoint in case it is connected to multiple endpoints.
>Any idea?
>zeromq-dev mailing list
>zeromq-dev at lists.zeromq.org

zeromq-dev mailing list
zeromq-dev at lists.zeromq.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20130929/7727b12d/attachment.htm>

More information about the zeromq-dev mailing list