Il 30/11/2012 18:54, Charles Remes ha scritto: > Marco, > > I think there is a fundamental misunderstanding about how a message queue is > supposed to work. If you haven't read the guide yet (zguide.zeromq.org) then > at the very least read this section: > > http://zguide.zeromq.org/page:all#Why-We-Needed-MQ > > The issues you describe are specific to your use-case. You need heartbeating > and ack'ing at the very minimum but you need to *build those concepts* on top > of zeromq. For example, if you don't want your client to process any more > messages if the server goes down, then you need to build a protocol between > your client and server so that it behaves that way. In that case, I would > have the server send only a single message at a time and wait for an ack from > the client before it could send another. Your client shouldn't ack until it > has processed the received message. > > As I said in the beginning, I think you are misunderstanding the purpose of > zeromq. Please read the guide.
I read the guide a lot of times, in particular the sections about Heartbeating. Of course I'm misunderstanding something in zmq. Perhaps all my applications need a workaround to get the thinks work right. My background is mainly related to MCU programming: I have difficulties to fully understand the behavior of the queues. Thank you for your patience! Marco _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
