Some differences I can think of offhand:

named pipes have a BYTE limit of about 4k, or so I'm led to believe from all
the documentation I've seen on pipes [maybe it's 16k or at best 64k, but in
any case, it also seems to be limited to "one or two messages" pending]

named pipes can ONLY be accessed on the local machine -- message files can
be accessed remotely via dsline/remote file equate

On the plus side, it might be easier to port unix programs that already make
use of "named pipes" using a pipe instead of subverting the program to use
message files...  (IOW, "select" should work on a named pipe...)

> -----Original Message-----
> From: Curtis Larsen [mailto:[log in to unmask]]
> Sent: Monday, November 20, 2000 4:20 PM
> To: [log in to unmask]
> Subject: MSG Files vs. Named Pipes?
>
>
> Are there any functional differences between a message file
> and a named
> pipe?
> When would you want one vs. the other?  (Papers?  Links?  FAQs?)
>
>
> Thanks!
> Curtis
>
>
>
> -----------------------------------------------------
> Confidentiality Notice: This e-mail transmission
> may contain confidential or legally privileged
> information that is intended only for the individual
> or entity named in the e-mail address. If you are not
> the intended recipient, you are hereby notified that
> any disclosure, copying, distribution, or reliance
> upon the contents of this e-mail is strictly prohibited.
>
> If you have received this e-mail transmission in error,
> please reply to the sender, so that we can arrange
> for proper delivery, and then please delete the message
> from your inbox. Thank you.
>