[boost] [asio] what happens to outstanding operations when demuxer::interrupt called?

From: Andrew Schweitzer (a.schweitzer.grps_at_[hidden])
Date: 2005-12-27 18:05:44

The doc seems to imply that if demuxer::reset() and demuxer::run() are 
called again, then outstanding operations will in fact be executed. Is 
this true?

Are there general design philosophies out there for handling things that 
happen way too late because the loop was paused? One system I worked on 
just fired all the stale timers at once, which I think what asio does. 
In the system I worked on, no effort was made to check whether the timer 
was firing hours too late.

Would it be reasonable to modify the timer completion handler to accept 
the amount of time "overdue" the current call of the handler is? This 
would at least allow the handler to check, but maybe that's too 
complicated.

There appears to be no general way to toss all work outstanding, is this 
  correct? I assume that's because it's hard to do so portably for all 
services.

On the other hand, it seems like maybe just deleting all your 
deadline_timer or stream_socket objects would cause them all to be 
cleaned up.