Martin, ignore my last comment, the user has no opportunity for breaking out of the (blocking) polling loop manually, so extrapolation would always be safe. Depending on the amount of unevenness, it would only use the absolute average frequency to set the extrapolation target well below the bounds of any physically conceivable possibility for overshoot.
On 4 September 2010 08:58, Martin Sustrik <[email protected]> wrote: > Naveen, > >> And if you want to be really safe, you can make it a "LOOP_OPTIMIZED" >> option, where the user knows that prematurely breaking from a polling >> loop with a timeout causes that timeout value not to be honoured >> correctly, and to use the "fail-safe" version to be certain. The >> "fail-safe" version can be enabled by default or vice versa. > > We've been trying to get rid of such magic options in 0MQ. Too much of them > and the product becomes unusable... :( > > I think we'll have to stick with time measurement per zmq_poll call and > allow users to create optimised algorithms -- such as one you've proposed -- > via ZMQ_FD and ZMQ_EVENTS socket options. > > Martin > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
