On Mon, Mar 26, 2012 at 6:27 PM, Chuck Remes <li...@chuckremes.com> wrote:
> On Mar 26, 2012, at 11:58 AM, Ian Barber wrote: > > > If 3.1 was an option and you wanted a tasty one socket set hack, you can > communicate credit via subscribe messages back up stream :) > > Absolutely. I would love to add this kind of "back channel" communication > so that we could have credit-based flow control built-in directly to libzmq > for all socket types. I'm hoping that some enterprising individual runs > with this idea as my C & C++ skills are probably not up to the task of such > an endeavor. > > cr > That functionality would need to live across transports and patterns, which is a slightly awkward cross cut to make in a standard way - you'd need a protocol change, unless you start coopting arbitary message parts to contain protocol information, which has proved kind of messy (though the whole label idea didn't really help there). It's almost something like the filter stuff sustrik is working on, but applied at the message accept level rather than pub/sub matching. I can see some value in having pluggable options there, as it would allow you to implement different queing/buffering schemes, and at least make it more of a pseudo-app that was putting stuff on and off of the message. Ian
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
