UNIX semantics do permit full support for asynchronous I/O

[Scott Schwartz]

In article <27813 at nuchat.UUCP> steve at nuchat.UUCP (Steve Nuchia) writes:
| >The POSIX.4 asynchronous I/O facilities are moving toward final ballot and
| >present a rich set of asynchronous I/O primitives.  These include the
| 
| It is precisely this "rich set" of "primitives" (!!!) that I am
| striving to avoid. 


I was just thinking the same thing.  Isn't it the case that
lightweight processes (mach style threads, say) with shared memory for
communication solve the asynch-io problem?  I'd prefer that to a new
set of async-io routines, I think.