On Mar 26, 2008, at 6:45 PM, Graham Leggett wrote:
Dirk-Willem van Gulik wrote:
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.
The Eclipse Job interface works like this, you basically say "run
this X ms from now", and if you want to run it again, you schedule
it again before you're done. The catch is that the timings aren't
that accurate, but then for most applications it doesn't need to be.
But that is just a matter of having clear semantics; i.e. 'run on, or
as soon as possible after'. Or 'try to run before'. And we should be
fine. The remainign issue is fragility; i.e. a task which aborts and
'forgets' to re-register is in pain.
Dw
