On Mar 26, 2008, at 5:35 PM, Graham Leggett wrote:
We could come up with something capable of spawning a dedicated process and/or thread every time there is a successful "tick" to run that tick, so that tick+1 isn't delayed if there is an overrun.
Or reduce the interface to a simple 'register callback 'at or before', or 'at or after' this time - and leave it up to the called entity to re-register itself.
It also helps prevent leaks, as the tick will have a pool that will be destroyed when the tick is complete and the thread/process terminates normally.
Dw
