Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!shelby!agate!usenet.ins.cwru.edu!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR)
Newsgroups: comp.lang.perl
Subject: Re: read/write pipe
Message-ID: <1991Mar2.021316.14234@NCoast.ORG>
Date: 2 Mar 91 02:13:16 GMT
References: <1991Feb23.202950.22171@uvaarpa.Virginia.EDU> <1991Feb23.205035.21729@convex.com>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR)
Followup-To: comp.lang.perl
Organization: North Coast Public Access Un*x (ncoast)
Lines: 24

As quoted from <1991Feb23.205035.21729@convex.com> by tchrist@convex.COM (Tom Christiansen):
+---------------
| From the keyboard of marc@mit.edu:
| :I know this has been mentioned here before, but I don't remember what
| :the reasons were.  Why is open(FOO,"|cat|") (a pipe to a program which
| :I can read from and write to) not supported?  
| 
| From the FAQ:
| 
|     20) How do I open a pipe both to and from a command?
| 
| 	In general, this is a dangerous move because you can find yourself in
| 	deadlock situation.  It's better to put one end of the pipe to a file.
+---------------

True, but there is a class of programs designed to work this way (like some
database servers, as marc@mit mentioned).

++Brandon
-- 
Me: Brandon S. Allbery			    VHF/UHF: KB8JRR on 220, 2m, 440
Internet: allbery@NCoast.ORG		    Packet: KB8JRR @ WA8BXN
America OnLine: KB8JRR			    AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY