Article View: comp.std.unix
Article #565Re: Standards Update, IEEE 1003.4: Real-time Extensions
From: Andy Glew
Date: Thu, 04 Oct 1990 06:21
Date: Thu, 04 Oct 1990 06:21
17 lines
1263 bytes
1263 bytes
Submitted-by: aglew@crhc.uiuc.edu (Andy Glew) >In the filesystem abstraction, you open a filename in one stage. You >can't do anything between initiating the open and finding out whether or >not it succeeds. This just doesn't match reality, and it places a huge >restriction on programs that want to do something else while they >communicate. Sounds like you want an asynchronous open facility, much like the asynchronous read and write that others already have on their wish list for file I/O (and other I/O) (not everyone believes that multiple threads are the way to do asynch I/O). -- Andy Glew, a-glew@uiuc.edu [get ph nameserver from uxc.cso.uiuc.edu:net/qi] Volume-Number: Volume 21, Number 181
Technical Details
Message-ID:
<13182@cs.utexas.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!jsqReferences:
<495@usenix.ORG> <523@usenix.ORG> <539@usenix.ORG> <541@usenix.ORG>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!jsq From: aglew@crhc.uiuc.edu (Andy Glew) Newsgroups: comp.std.unix Subject: Re: Standards Update, IEEE 1003.4: Real-time Extensions Message-ID: <13182@cs.utexas.edu> Date: 4 Oct 90 06:21:55 GMT References: <495@usenix.ORG> <523@usenix.ORG> <539@usenix.ORG> <541@usenix.ORG> Sender: jsq@cs.utexas.edu Organization: Center for Reliable and High-Performance Computing University of Lines: 17 Approved: jsq@cs.utexas.edu (Moderator, John S. Quarterman) X-Submissions: std-unix@uunet.uu.net