Martin, Thanks for letting us know, I will change the Python bindings.
Cheers, Brian On Sat, Mar 13, 2010 at 7:18 AM, Martin Sustrik <[email protected]> wrote: > Hi all, > > Today I've removed ZMQ_NOFLUSH and zmq_flush implementation from > 0MQ/2.0. The rationale for the change is as follows: > > 1. zmq_flush() looked like an equivalent of POSIX fflush and thus it was > confusing to 0MQ users. > > 2. zmq_flush() was usable only in very small percentage of use cases > (loads over 1M msgs/sec + business logic allowing for message batching > on application layer), yet it used significant part of API real estate. > > 3. The same functionality will be doable in different way in the future > (multi-part messaged). > > Upcoming release (2.0-beta3) will still define the symbols (zmq_flush > and ZMQ_NOFLUSH) in zmq.h, thus the language bindings won't break. The > documentation concerning the feature is removed though. > > Following version (2.0-beta4) will remove the symbols from zmq.h, thus > the language bindings have to be changed accordingly in the meantime. > (I've already changed Java and Ruby bindings that I am maintaining.) > > Sorry for annoyance! > Martin > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > -- Brian E. Granger, Ph.D. Assistant Professor of Physics Cal Poly State University, San Luis Obispo [email protected] [email protected] _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
