Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.unix.wizards
Subject: Re: The 4.3 BSD awrite() solution
Message-ID: <1.P1XZCxds13@ficc.uu.net>
Date: 12 Feb 90 22:40:35 GMT
References: <1055.18:35:28@stealth.acf.nyu.edu> <131445@sun.Eng.Sun.COM> <6068:00:23:14@stealth.acf.nyu.edu> <131606@sun.Eng.Sun.COM>
Reply-To: peter@ficc.uu.net (Peter da Silva)
Distribution: usa
Organization: Xenix Support, FICC
Lines: 9

In article <131606@sun.Eng.Sun.COM> lm@sun.UUCP (Larry McVoy) writes:
> So let's consider your stuff again.  You claim that you've implemented
> awrite().  So what's awrite()?

awrite(fd, buf, n) initiates a write of n bytes from buf, returning
immediately. It returns some token that you can use to tell when the
write is complete and get the number of bytes actually written. You also
need to be able to wait on completion, and a close would implicitly
perform such a wait.
-- 
 _--_|\  Peter da Silva. +1 713 274 5180. <peter@ficc.uu.net>.
/      \
\_.--._/ Xenix Support -- it's not just a job, it's an adventure!
      v  "Have you hugged your wolf today?" `-_-'