i’m sorry, maybe i skippe dteh very start of this thread, but why are we even considering heartbeating using transport layer stuff? it seems contrary to the spirit of zmq and its orthogonality to transport choice.
is the driving use case documented/described somewhere? On Jan 3, 2014, at 9:31 AM, Lindley French <[email protected]> wrote: > There are two approaches that can be used if an API specifies time more > finely than the system supports. > > First, you can specify in the API that this is only a hint. This is accurate > but it makes it more difficult to reason about and debug the actual behavior. > > Second, you can have the method return the actual value that will be used, > which might be different than the value requested. > > > On Fri, Jan 3, 2014 at 5:54 AM, KIU Shueng Chuan <[email protected]> wrote: > What should be the behavior if the user specifies 1500ms but the underlying > OS only supports seconds granularity? > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev ----------------------- Andrew Hume 949-707-1964 (VO and best) 732-420-0907 (NJ) [email protected]
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
