Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!mordor!lll-tis!ptsfa!hoptoad!academ!uhnix1!sugar!karl
From: karl@sugar.UUCP (Karl Lehenbauer)
Newsgroups: comp.sys.amiga
Subject: Re: MCC pipes, and what do SysV named pipes really do?
Message-ID: <209@sugar.UUCP>
Date: Fri, 19-Jun-87 19:27:55 EDT
Article-I.D.: sugar.209
Posted: Fri Jun 19 19:27:55 1987
Date-Received: Thu, 25-Jun-87 06:33:00 EDT
References: <1174@crash.CTS.COM> <279@louie.udel.EDU> <3872@jade.BERKELEY.EDU> <1218@crash.CTS.COM>
Organization: Sugar Land UNIX - Houston, TX
Lines: 13
Keywords: usg System V named pipes fifos

> Actually, you do hang if the pipe is full.  This makes System V named pipes
> essentially useless in my opinion.  The main application I see for them is something
> like a spooler queue.  But if the server reading the pipe is busy, and several
> clients append their requests to the pipe, it becomes full, and the next attempt
> to queue a request will block.  

I don't see that hanging on full pipes makes them useless, other than for
realtime.  After all, hanging's what unnamed ones do.  If you don't want
programs to hang (very long) on a named pipe, have a receiver sit there reading
the thing constantly and buffer the data somewhere.
-- 
uucp: {shell,rice,seismo}!soma!uhnix1!sugar!karl
bbs:  (713) 933-2440	voice: (713) 933-9134