Hi Martin,
> -----Original Message-----
> From: Martin Sustrik [mailto:[email protected]]
> Sent: Tuesday, August 31, 2010 9:49 AM
> To: 0MQ development list
> Cc: Kelly Brock; '0MQ development list'
> Subject: Re: [zeromq-dev] Limitations of patterns?
>
> On 08/31/2010 02:14 PM, Kelly Brock wrote:
>
> > So, the point of this was to reduce the case of major task pileups.
> > Additionally I "hope" we could solve for the broader usage and allow a
> first
> > come, first serve distribution on push without the queued messages. I
> just
> > don't see how to get that without a separated ack ability. :/
>
> Well, you can limit the number of messages on flight to 2 even without
> user-level acks: Max one message in the queues can be guaranteed by HWM.
> One more message can be processed by the application.
Yup, still leaves 10 messages in a waiting state though, which is
the only thing I'm concerned with in this particular case. If this is
inappropriate for push to worry about, that's fine. As Matt outlined, there
are other ways to do it.
If this is not appropriate to zmq push, I would suggest making a
utility library of "patterns" that support the more complicated cases. For
my case it would be a first come/first serve with no queuing since my tasks
are very random in time, Matt's outline sounded about right for my work
around. Of course, zmq is not intended for what I'm using it for at work,
it just happened to "mostly" fit the bill. :)
KB
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
