[zeromq-dev] architecture

Benoit Chesneau bchesneau at gmail.com
Tue Jan 25 01:12:14 CET 2011

On Tuesday, January 25, 2011, Pieter Hintjens <ph at imatix.com> wrote:
> On Mon, Jan 24, 2011 at 11:51 PM, Benoit Chesneau <bchesneau at gmail.com> wrote:
>> Hum I should be tired, PUSH/PULL works as expected. Now the only thing
>> I miss i s a way to remove a connection from the push socket. Ca I do
>> this ?
> Not really. If you want two-way communication and synchronization
> between workers and clients (your services?) then you need an XREQ
> routing architecture.
> -Pieter

I tbink you'r right. If I want to keep ly current pattern, what I want
is probably xreq -> rep. The thing I'm not sure about is how the xreq
socket deals with a disconnectd rep. What happend to the messge he
has? Does it try to send them in newly connected node?

Other solution i see is to intoduce a broker. In above case each
"papa" were registering in a redis db. I will write some code later
today. (1am here). Hopefully I will release this tiny project tonight.

Thanks for the help anyway, also I really appreciate the documentation :)

- benoît

More information about the zeromq-dev mailing list