home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Usenet 1994 October
/
usenetsourcesnewsgroupsinfomagicoctober1994disk2.iso
/
std_unix
/
v21
/
131
< prev
next >
Wrap
Internet Message Format
|
1990-12-05
|
2KB
From std-unix-request@uunet.uu.net Tue Sep 25 16:34:14 1990
Received: from cs.utexas.edu by uunet.uu.net (5.61/1.14) with SMTP
id AA16616; Tue, 25 Sep 90 16:34:14 -0400
Posted-Date: 25 Sep 90 16:44:28 GMT
Received: by cs.utexas.edu (5.64/1.76)
From: henry@zoo.toronto.edu (Henry Spencer)
Newsgroups: comp.std.unix
Subject: Re: Standards Update, IEEE 1003.4: Real-time Extensions
Message-Id: <543@usenix.ORG>
References: <495@usenix.ORG> <523@usenix.ORG> <539@usenix.ORG> <541@usenix.ORG>
Sender: jsq@usenix.ORG
Organization: U of Toronto Zoology
X-Submissions: std-unix@uunet.uu.net
Date: 25 Sep 90 16:44:28 GMT
Reply-To: std-unix@uunet.uu.net
To: std-unix@uunet.uu.net
Submitted-by: henry@zoo.toronto.edu (Henry Spencer)
In article <541@usenix.ORG> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>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.
Programs that want to do two things at once should use explicit parallelism,
e.g. some sort of threads facility. In every case I've seen, this yielded
vastly superior code, with clearer structure and better error handling.
--
TCP/IP: handling tomorrow's loads today| Henry Spencer at U of Toronto Zoology
OSI: handling yesterday's loads someday| henry@zoo.toronto.edu utzoo!henry
Volume-Number: Volume 21, Number 131