[zeromq-dev] Requirements for reliability

Martin Sustrik sustrik at 250bpm.com
Wed Apr 7 18:31:34 CEST 2010

Apps, John wrote:

> 1 and 2 MUST be reliable, i.e., they are in essence a transaction.
> (Legally, the ticket is as good as whatever the prize happens to be
> -potentially millions- until such time as the draw has taken place.)
>  One could argue that the onus of ensuring consistency lies in the
> code written on client and server; however, I think that is what the
> idea of 'reliability' in this context is meant to avoid?

I would say so.

This is actually the simplest possible scenario I've spoke of couple of 
emails back. It boils down to fully synchronous "send a request a block 
until transaction is processed". This case is rather simple and easy to 
start with. Yet it covers most use cases for "reliability".


More information about the zeromq-dev mailing list