[zeromq-dev] flushing queues
matt_weinstein at yahoo.com
Fri Aug 27 21:18:31 CEST 2010
Sorry I'm on the road, but a quick (not particularly organized) set of
Briefly, 0MQ provides an efficient way to move data -- lockless pipes
and buffer structures -- and a nice interface abstraction. You are
likely to get the same guarantees as the underlying machinery that 0MQ
uses, whether network, process scheduling, or ...
You can't really know you've received the last message unless you read
something that follows it in order, it's the usual tachyon dilemma :-)
You can do things like close down sockets are threads when you see a
particular state message, which can provide information "in a
different way" in the synchronization space, but you're always back to
managing asynchronous state....
On Aug 27, 2010, at 12:52 PM, Andrew Hume wrote:
> does 0MQ provide any temporal guarantees about delivery of messages?
> or a way to probe if all teh messages queued for a socket have been
> Andrew Hume (best -> Telework) +1 732-886-1886
> andrew at research.att.com (Work) +1 973-360-8651
> AT&T Labs - Research; member of USENIX and LOPSA
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the zeromq-dev