Cool, that makes a lot of sense. Thank you Pieter and Martin for the very helpful responses. I've learned a lot in a short time, and I look forward to seeing what comes of all this in newer versions of 0MQ.
Cheers, Marcelo On 15 October 2010 02:19, Pieter Hintjens <p...@imatix.com> wrote: > On Thu, Oct 14, 2010 at 3:18 PM, Marcelo Cantos > <marcelo.can...@gmail.com> wrote: > > > My apologies in advance if I've misunderstood what Pieter is saying, but > the > > above statement doesn't sit right with me. Blocked applications are > either > > effectively dead because they have entered an endless loop, or are simply > > taking an awfully long time to compute the billionth digit of pi. > > Sure, this is why heartbeating should be configurable. In some > applications it has to be 1/10th of a second, in others it should be > 60 seconds or more. > > In some cases (pipeline, pubsub) heartbeats can only work at the > transport level. > > In other cases you do need heartbeats at the application level as > well. So IMO we'll need them both in the tcp:// transport and on top > of that in some use cases. > > -Pieter > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
