[zeromq-dev] Fine control in the ROUTER socket

[Michael Alexopoulos]

Pieter Hintjens <ph <at> imatix.com> writes:

> 
> On Tue, Apr 23, 2013 at 10:57 AM, Andrey Ushenin <andrey_ushenin <at> 
yahoo.co.uk> wrote:
> 
> 
>  
> 
> 2. related to #1: is it possible to have a watermark individually 
counted in the ROUTER socket for each attached client?
> 
> 
> 
> 
> Not sure what you are asking here.
> 
> 
> 
> 
> 
> 3. More general question - is DEALER-ROUTER setup as we use them the 
best way to implement our requirements? I'm wonderting if there are any 
alternatives where we could still use the routing functionality like the 
one provided by the ROUTER but have a more control over individual client 
pipes. 
> 
> 
> 
> 
> 
> 
> 
> 
> In Zyre, we use a ROUTER for incoming messages but send all outgoing 
messages on a DEALER, one per peer. This lets us be very precise about 
e.g. closing the DEALER socket when we think a peer has died. We use the 
ROUTER identity ask key to hold an object per peer, which includes its 
DEALER socket.
> 
> 
> -Pieter
> 
> 
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev <at> lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> 

Hello Pieter,

   I think another way to pose the question might be,

"How does one get a handle to the client socket which got accepted via the 
ROUTER socket listening to a specific address for incoming client 
connection requests?"

I'm thinking along the lines of the classic TCP paradigm here, whereby the 
process which makes the listen() call will respond on a client connect() 
request by calling accept() and get back a file descriptor which is a 
handle to the newly created client socket.



Thanks