On Sat, Dec 10, 2011 at 3:08 AM, Martin Sustrik <[email protected]> wrote: > Hi all, > > My proposal thus is to use rate control to control the behaviour. For > example, user can set ZMQ_RATE to 10Mb/s and is expected to ensure that > the network is capable of that load.
I think your rate based approach sounds great. > 1. The I/O thread will extract messages from the pipe at rate of 10Mb/s. > The network should be able to handle the load, so pushing these messages > into the network shouldn't be a problem. If it happens to be a problem, > I/O thread will start dropping messages so that draining of the pipe > continues at 10Mb/s. > > 2. The application thread will push massages to the pipe and if the pipe > is full it will *block*. > Thoughts? Does anyone see any problem with this approach? > What would happen if the socket was constructed with a non-blocking option? Would it set EAGAIN, or should a new error like ERATELIMIT be set? -Mike _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
