home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!uunet!not-for-mail
- From: karish@pangea.stanford.edu (Chuck Karish)
- Newsgroups: comp.std.unix
- Subject: Re: asyncronous I/O notification in POSIX: a question
- Date: 27 Aug 1992 18:05:06 -0700
- Organization: Mindcraft, Inc.
- Lines: 30
- Sender: sef@ftp.UU.NET
- Approved: sef@ftp.uucp (Moderator, Sean Eric Fagan)
- Message-ID: <17ju42INN8eg@ftp.UU.NET>
- References: <17jq1lINN7gc@ftp.UU.NET>
- NNTP-Posting-Host: ftp.uu.net
- X-Submissions: std-unix@uunet.uu.net
-
- Submitted-by: karish@pangea.stanford.edu (Chuck Karish)
-
- In article <17jq1lINN7gc@ftp.UU.NET> pdh@netcom.com (Phil Howard ) writes:
-
- >What I cannot find or cannot figure out is how the process that has
- >received the EAGAIN code from [a non-blocking read() or write()] is
- >going to be
- >able to be notified of the fact that I/O is now completeable when that
- >condition exists, and how it can find out which file descriptor(s) has
- >the I/O ready (of probably 2 or more in cases where the benefit of the
- >asyncronous I/O is helpful).
- >
- >The mechanism I use in BSD is the select() function.
-
- The description of [EAGAIN] in POSIX.1 is:
-
- [EAGAIN] Resource temporarily unavailable
- This is a temporaty condition, and later calls to
- the same routine may complete normally.
-
- The portable way to find out whether the resource has become
- available (modem connection completed, data ready, memory available,
- etc.) is to wait a while, then try again.
- --
-
- Chuck Karish karish@mindcraft.com
- (415) 323-9000 x117 karish@forel.stanford.edu
-
-
- Volume-Number: Volume 29, Number 15
-