Xref: utzoo comp.lang.misc:5426 comp.unix.wizards:23707
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!rpi!uupsi!ccavax!merriman
From: merriman@ccavax.camb.com
Newsgroups: comp.lang.misc,comp.unix.wizards
Subject: Re: UNIX semantics do permit full support for asynchronous I/O
Message-ID: <31445.26dc0466@ccavax.camb.com>
Date: 29 Aug 90 22:07:34 GMT
References: <126800008@.Prime.COM> <60345@lanl.gov> <1990Aug21.223350.7595@esegue.segue.boston.ma.us> <11576:Aug2503:18:3790@kramden.acf.nyu.edu> <27619@nuchat.UUCP> <1990Aug29.170931.10853@terminator.cc.umich.edu>
Distribution: usa
Organization: Cambridge Computer Associates, Inc.
Lines: 9

In article <1990Aug29.170931.10853@terminator.cc.umich.edu>, 
	rsc@merit.edu (Richard Conto) writes:

> 
> Make it simpler. Have a routine that requests an I/O operation. Another
> routine that can check it's status. A way of specifying a routine to be
> called when the I/O operation completes might be yet another option.

Sure sounds like VMS QIO calls.