From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,3e11ef4efc073f6b
X-Google-Attributes: gid103376,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!postnews.google.com!r15g2000prh.googlegroups.com!not-for-mail
From: christoph.grein@eurocopter.com
Newsgroups: comp.lang.ada
Subject: Re: requeue with abort and timed call
Date: Tue, 30 Dec 2008 05:18:58 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <0f9bf864-927b-442c-a435-1713c40cfd30@r15g2000prh.googlegroups.com>
References: 
 <2a60b044-6a5c-4ce6-93e6-6eeefc8806c3@l33g2000pri.googlegroups.com>
	<1f6rcb1qwt7vx.1mckzyk9ucohf.dlg@40tude.net>
 <84c56781-1cb1-4d86-be14-e66fc9fdade6@w1g2000prk.googlegroups.com>
	<7p8onuvzdz18$.1m1dq8n3b52q5.dlg@40tude.net> <9j9ajg.3a7.ln@hunter.axlog.fr>
	<2a0a1de3-6736-4478-9378-50b8895fa20d@r15g2000prh.googlegroups.com>
	<kepcjg.od.ln@hunter.axlog.fr>
NNTP-Posting-Host: 91.13.254.227
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: posting.google.com 1230643138 18079 127.0.0.1 (30 Dec 2008 13:18:58
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Tue, 30 Dec 2008 13:18:58 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: r15g2000prh.googlegroups.com; posting-host=91.13.254.227;
	posting-account=rmHyLAoAAADSQmMWJF0a_815Fdd96RDf
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.5)
	Gecko/2008120122 Firefox/3.0.5,gzip(gfe),gzip(gfe)
Xref: g2news2.google.com comp.lang.ada:4095
Date: 2008-12-30T05:18:58-08:00
List-Id: <comp.lang.ada>

On 30 Dez., 10:25, Jean-Pierre Rosen <ro...@adalog.fr> wrote:
> No. A timed entry call means: "if the server does not arrive within XX
> seconds, I give up". Requeue (with abort) allows the server to get the
> request, inspect the parameters, and decide that this request cannot be
> serviced now and put it back on wait. This is transparent as seen from
> the client's side.

So what you say here is that the delay is still active in the time
line I gave in a previous post and Requeued_Call must be aborted? If
so, GNAT is definitively in error.

> Time line is like following;
>  0.0 The call of Original_Call
> *1.0 The expiration time of original call, so no abort, because in
> rendezvous
>  3.0 Complete Original_Call
> *3.0 Queued on Requeued_Call, which is never serviced, but which is
> also not abortable (no delay active).

> So I do not see a problem with the behavious as shown in the OP's
> example.

> *3.0 Queued on Requeued_Call - hm, you think the delay is still
> active? We need a language lawyer to enlighten us.

I guess this should be put to Ada-Comment for a definitive answer by
Ada mainainers (Randy, Tuck, etc.).