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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE, MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4 Xref: utzoo comp.edu:2908 comp.lang.ada:3173 comp.lang.misc:3891 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!samsung!munnari.oz.au!uniwa!wacsvax!kim From: kim@wacsvax.OZ (Kim Shearer) Newsgroups: comp.edu,comp.lang.ada,comp.lang.misc Subject: Re^2: Teaching Concurrency Message-ID: <1497@wacsvax.OZ> Date: 14 Jan 90 12:33:09 GMT References: <7588@hubcap.clemson.edu> <602@agcsun.UUCP> Organization: Comp Sci, Uni. Western Australia. List-Id: meissner@osf.org (Michael Meissner) writes: >In article <10330@june.cs.washington.edu> pattis@cs.washington.edu (Richard Pattis) writes: >| OK, so this begs the question: what is the "smallest" assignment that can >| use concurrency fruitfully. I would like to teach a bit about tasking in >| one of my classes, but I don't want students to get "wrong" ideas from the >| example I use. Anyone out there have such an assignment? Is there some prime >| example out there of a good use of multi-tasking that is amenable to >| classroom instruction? Another simple real worldish type example would be a centrally controlled distributed monitoring system. This is actually pinched from a computer controlled irrigation monitoring system I worked on in ADA. The idea is that you have a number of fairly dumb monitoring tasks which report to a central controlling program. The central system accepts input from the monitoring tasks and sends a simple reply. The input and output could be very simple and very synthetic. The real tasking comes as the student would need to produce input and output routines to coordinate the input from and output to multiple monitors. The students could be provided with a simple monitor program to set up n times, and asked to write the central controller that conforms to some simple protocol.