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,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,37f13de4a5a41a8,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-03-31 05:18:24 PST
Path: archiver1.google.com!postnews1.google.com!not-for-mail
From: simon_the_softy@hotmail.com (Simon Apperley)
Newsgroups: comp.lang.ada
Subject: Elegant 'abort' of sleeping task
Date: 31 Mar 2003 05:18:20 -0800
Organization: http://groups.google.com/
Message-ID: <310b040f.0303310518.76dc9bf7@posting.google.com>
NNTP-Posting-Host: 193.195.213.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1049116702 2902 127.0.0.1 (31 Mar 2003 13:18:22
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 31 Mar 2003 13:18:22 GMT
Xref: archiver1.google.com comp.lang.ada:35825
Date: 2003-03-31T13:18:22+00:00
List-Id: <comp.lang.ada>

Hi,

I'm looking at the design of a piece of server code which has to
handle calls that also pass a timeout value. The target system is
aerospace related, and dynamically creating tasks 'on the fly' just is
not an option.

I want to be able to set up a single task to handle the timeout from
the head of a delta-queue of timeouts, but have found a problem. If I
have the timeout implemented as a task stuck in a 'delay' call, and a
more immediate timeout comes in, I want to wake up the sleeping task,
re-calculate the delta-queue and then sleep on the new, shorter,
delay. So far the only way I can see to do this is to use abort, and
set up the task again, which seems a bit of a brute force approach.

Has anyone got any suggestions on how I can interrupt the sleep call,
without using a polling approach that would just consume CPU time at
the expense of the other code in the system.

I could use direct calls to the underlying RTOS, but I'd rather keep
as much as possible within the Ada language.

I did wonder about delay until TIME, and having another task change
TIME, but that seems rather un-safe to me as it starts making
assumptions about the underlying run-time implementation.

Thanks

Simon Apperley @ General Dynamics UK COM