I looked at the method description for
tick(min, max), it says:
"Blocks up to "minimum"
seconds until a callback delivery, then..."
Does that mean that if there is one
callback (message) waiting, tick(min, max) will return immediately after
that callback is called?
But if there's no callback, tick(min, max) will wait at least min seconds?
Michael
Dipl.-Inf. Michael Raab
Fraunhofer-Institut für Fabrikbetrieb und -automatisierung IFF
Virtuell Interaktives Training
Sandtorstr. 22, 39106 Magdeburg, Germany
Telefon +49 (0) 391/ 40 90 122
Telefax +49 (0) 391/ 40 90 115
address@hidden http://www.iff.fraunhofer.de
oder http://www.vdtc.de
Von:
Eric Noulard <address@hidden>
An:
CERTI development discussions
<address@hidden>
Datum:
11/15/2010 03:31 PM
Betreff:
Re: [certi-dev]
Tick usage
Gesendet von:
address@hidden
2010/11/15 Michael Raab <address@hidden>:
> Hi Eric,
>
> I'm a little bit confused about tick(min, max) calls. To me it seems
that
> tick() doesn't block the specified min time. Seems that it returns
once at
> least one callback could be executed?!
Normally it shouldn' t do that.
It will handle callback "as they come" and continue "tick-processing"
until "min" time occurs.
So , you may see callback coming **before** the tick(min, max) returns,
now the resolution of the clock drive the precision off the timeout.
(have a look at ClockFactory.cc or run the TestClocks test program
in order to have more informations about clock resolution)
I think but I need to check that the default parameter-less tick
do only process 1 callback, unless you compile CERTI with HLA13NG_LIBRTI.