[zeromq-dev] Survey: use of 0MQ request reply

Maciej Gajewski Maciej.Gajewski at tibra.com
Thu Jun 16 09:06:20 CEST 2011

> 1. Are you using ROUTER (XREP) sockets in custom devices or brokers?

Yes, to distribute incoming requests to workers. Workers simply ignore the first message part and prepend it to every response.

>2. Are you using ROUTER sockets in end-nodes (application code)? If so, can you explain how and why?

Yes, for asynchronous server serving multiple clients.

> 3. Are you using DEALER sockets in end-nodes? If so, can you explain how and why?

Yes, for asynchronous, client connected to one or more servers.

> 4. Are you using the REQ-REP multi-hop functionality, either with a queue device, or a custom device? Can you explain how and why?

No. I possibly would but I'm not sure I understand it properly. The guide aims to exhaustive, but it is to detailed and verbose, while reference is to sparse. I think simple table or 'custom routing cheat sheet' would be more useful.

> 5. How do you handle failures (lost requests or replies)?
Using deadline timers to detect replies w/o requests. Either retrying or fataling (depending on app).

> 6. Anything you feel is missing or inadequate in the REQ/REP designs? Please explain with a use case.

Ability to get more info on connected clients/servers. There is no way of telling to how many peers a socket is connected and to get any parameters of those.

Tibra Trading Europe Limited is Authorised and Regulated by the FSA (Company No. 06061713)
Tibra Global Services Pty Limited London Branch (Company No. BR014370)
Tibra Equities Europe Limited (Company No. 07283912)
Registered in England & Wales - Level 11, 5 Aldermanbury Square London EC2V 7HR

The contents of this email including any attachments are confidential.  If you have received this email in error, please advise the sender by return email and delete this email.  Any unauthorised use of the contents of the email is prohibited and you must not disseminate, copy or distribute the message or use the information contained in the email or its attachments in any way.

The views or opinions expressed are the author's own and may not reflect the views or opinions of Tibra. Tibra does not guarantee the integrity of any emails or attached files. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments.

More information about the zeromq-dev mailing list