Re: [reSIProcate] Timers: why system time?
I think a solution that does not depend on how often getTimeMs is
called is preferred, given that it doesn't have a huge hit on
performance. This makes the Timer class more usable as a general
utiltiy fn, if used outside of the stack.
Scott
On Wed, Nov 5, 2008 at 2:26 PM, Alexander Altshuler <alt@xxxxxxxxx> wrote:
> Hi All
>
> The requirements for offered Win32 timer wrap around problem:
> Timer::getTimeMs() must be reasonable often called.
>
> The solution:
> - redefine SipStack::getTimeTillNextProcessMS() that it will return
> 0xfff maximum for example.
>
> PS: Timer::msTillNextWrapAroundTimer() stuff I posted today will be
> unnecessary.
>
> Regards
> Alexander Altshuler
> http://xeepe.com
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>