Re: requeue with abort and timed call

[Jean-Pierre Rosen <rosen@adalog.fr>]

Dmitry A. Kazakov a �crit :
> On Sun, 28 Dec 2008 07:53:44 -0800 (PST), christoph.grein@eurocopter.com
> wrote:
> 
>> I do not see a problem with aborting. Why should the entry call be
>> aborted?
> 
> Because the request remains *queued* after expiration of the timed entry
> call.
> 
There seems to be some confusion about terms here.

For a timed entry call, the call is /cancelled/ if the it is not 
accepted within the given time span. If the call has been requeued, it 
is the beginning of the second accept that determines the deadline.

However, there is no /abort/ in this example. The "with abort" in the 
requeue statement really means that the rendezvous will start over from 
scratch, implying that the queued task could be aborted (or cancelled by 
a timed entry call, or asynchronous transfer of control). Without the 
"with abort", the second queue is considered as within the first 
rendezvous, and a caller is abort-deferred during a rendezvous (and 
since it is the acceptance time that matters for timed entry call, it 
will be too late to cancel the call).

Anyway, it is clear that the second call should be cancelled in this 
example.
-- 
---------------------------------------------------------
            J-P. Rosen (rosen@adalog.fr)
Visit Adalog's web site at http://www.adalog.fr