Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!caen!gilgalad
From: gilgalad@caen.engin.umich.edu (Ralph Seguin)
Newsgroups: comp.sys.amiga.tech
Subject: Re: PIPEs
Keywords: PIPE, IP-Device
Message-ID: <1990Nov2.173103.18889@engin.umich.edu>
Date: 2 Nov 90 17:31:03 GMT
References: <1990Oct19.044319.4851@engin.umich.edu> <1990Nov2.091542.25505@agate.berkeley.edu>
Sender: news@engin.umich.edu (CAEN Netnews)
Distribution: na
Organization: University of Michigan Engineering, Ann Arbor
Lines: 21

In article <1990Nov2.091542.25505@agate.berkeley.edu> pete@violet.berkeley.edu (Pete Goodeve) writes:
>
>In  <1990Oct19.044319.4851@engin.umich.edu>,
>Ralph Seguin (gilgalad@caen.engin.umich.edu) asks:
>> Does anybody know whether or not Amiga OS 2.0 will support "true pipes",
>> ie pipes ala UNIX?  I am considering writing a true pipe handler, but
>> I don't want to waste my time if C= is going to do it for me 8-).
>>
>[I think this topic crops up afresh every month or so, but never mind...]
>OK -- what exactly ARE the criteria for "true" pipes?  Or at least, which
>do you find necessary?   I've always felt that the form of unix pipes was

The major problem with any of the pipe implementations for the Amiga is
that they build "named" temporary files.  Kinda bad, when you're trying
to use pipes as an IPC with files larger than a megabyte.  For instance:

ilbmtoppm blah.iff|ppmquant 256|ppmscale -yscale 1.4|ppmtogif >blah.gif

Hmmm... Let's see, that's 3 megs worth of temp files.

			See ya, Ralph