Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!jade!eris!mwm From: mwm@eris.UUCP Newsgroups: comp.sys.amiga Subject: Re: Pipes Message-ID: <2337@jade.BERKELEY.EDU> Date: Sat, 24-Jan-87 22:34:00 EST Article-I.D.: jade.2337 Posted: Sat Jan 24 22:34:00 1987 Date-Received: Sun, 25-Jan-87 14:45:34 EST References: <946@tekred.UUCP> Sender: usenet@jade.BERKELEY.EDU Reply-To: mwm@eris.BERKELEY.EDU (Mike Meyer) Organization: Missionaria Phonibalonica Lines: 15 In article <946@tekred.UUCP> joels@tekred.UUCP (Joel Swank) writes: >>The key thing about a pipe is that it's a FIFO queue, with a limited >>buffer size. > >The real advantage of pipes over files that imitate them is that all >processes in the chain can run simultaneously. Which also means that the processes can overlap I/O and processing with each other, so that the group takes less wall-clock time than it would if you had to run them sequentially. Ain't real pipes neat things? Of course, to get this advantage, you gotta have true multitasking....