Re: AsyncCall API notes

From: Alex Rousskov <rousskov_at_measurement-factory.com>
Date: Wed, 10 Sep 2008 15:21:29 -0600

On Wed, 2008-09-10 at 22:39 +0200, Henrik Nordstrom wrote:
> On ons, 2008-09-10 at 11:38 -0600, Alex Rousskov wrote:
>
> > * It is not a bug to cancel something late, but the canceling code
> > should be aware of that possibility. Canceling something late is a
> > no-op.
>
> Can you define "late"?

It is defined above the paragraph you quoted. Here is the relevant text:

* Cancellation has immediate effect (i.e., the call will never be dialed
after cancel() is called), but cancellation may be "late" if the call
has already been dialed (i.e., the call is or was alive).

> Is this after the call has been queued, or after it has been dialed?
>
> Should be after it's dialed..

It is, but I am obviously failing to relay that. I will define "late
cancellation" as a separate bullet and polish the wording.

Thanks,

Alex.
Received on Wed Sep 10 2008 - 21:22:18 MDT

This archive was generated by hypermail 2.2.0 : Thu Sep 11 2008 - 12:00:12 MDT