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=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Structure of the multitasking server
Date: Sat, 14 Mar 2015 08:22:33 +0000
Organization: A noiseless patient Spider
Message-ID: <ly7fukrnsm.fsf@pushface.org>
References: 
 <8b4d1170-22e6-40d3-8ed1-096dc0163491@m36g2000hse.googlegroups.com>
	<ho90bg.gnt.ln@hunter.axlog.fr>
	<71b51c8e-6bed-4156-9f52-31bef57b8575@googlegroups.com>
	<871tktuc9i.fsf@adaheads.sparre-andersen.dk>
	<bf5e1244-c5cb-475b-8555-de190aae4ae8@googlegroups.com>
	<uu0on2a375l0.1lixh9dqxrbh5.dlg@40tude.net>
	<c943b1fd-8c0c-4c22-ba8c-fb72fbd52805@googlegroups.com>
	<mdvqeb$492$1@loke.gir.dk>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org;
 posting-host="c266ac6a7b23adb6fddc6455356f7788";
	logging-data="14898"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19Z5W8Y6SUh3qaL/6XM1mRXfTurA2MSSMs="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (darwin)
Cancel-Lock: sha1:aUgH9mQmmaadTDcyYrNSphQkvyA=
	sha1:BYNLar33xZNDBW41WkMo/plfiXU=
Xref: news.eternal-september.org comp.lang.ada:25172
Date: 2015-03-14T08:22:33+00:00
List-Id: <comp.lang.ada>

"Randy Brukardt" <randy@rrsoftware.com> writes:

> Of course, if there is a queue of jobs anyway, it makes sense to
> arrange that to be blocking so you end up waiting on that. But then of
> course you need a "stop" job else the supervisor ends up waiting
> forever.

Having the supervisor wait forever is OK in some circumstances
(particularly in embedded systems). Though I had to introduce one to
support offline tests (you need to be able to go on to the next test!)