Re: requeue with abort and timed call

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

christoph.grein@eurocopter.com a �crit :
> So if I understand correctly, the behaviour can be summarized as
> follows in times Ti:
> 
> T0:          timed entry call E1 with delay Delta
> T1:          rendezvous E1 starts
> T2=T0+Delta: delay expires, but since E1 is executing, rendezvous
> continues
> T3:          requeued with abort to E2 and rendezvous E1 ends
> 
> We now have to distinguish two cases:
> 
> 1. E2 is ready for rendezvous:
> 
> T3 cont'ed: Entry call E2 is not queued, instead rendezvous E2 starts
>             immediately, so entry call of T0 is not cancelled.
>             From the client's point of view, the entry call terminates
>             normally (because the client is unaware of the requeue).
> 
> 2. E2 is not ready for rendezvous:
> 
> T3 cont'ed: Entry call E2 is queued. Since the delay has already
>             expired at T2, the entry call E2 is immediately cancelled,
>             i.e. taken out of the queue again.
>             This is the cancellation of the timed entry call at T0
>             because the call did not start before the expiration
>             (in fact, it's the call of E2 that did not start before
>             T2, but the client is unaware of the requeue).
> 
> Is this correct?
Yes, this is a nice summary

-- 
---------------------------------------------------------
            J-P. Rosen (rosen@adalog.fr)
Visit Adalog's web site at http://www.adalog.fr