2

I am working on a inter processes communication. I came across named pipe communication.

I already have some basic idea but need to make sure the following points?

  1. Does name pipe can have more than one client at a same time?

  2. Does it supports communication over different process build on different languages.

And please do tell me that what is the difference between named pipe communication and broadcasting for inter process communication ?

shujaat siddiqui
  • 1,527
  • 1
  • 20
  • 41

1 Answers1

5

No, a single pipe only supports a single client. Much like a web server, it also creates multiple connections to each individual client. A pipe server works the same way.

Yes, bridging the wall between processes is a major use case for named pipes.

Windows supports a different object for broadcasting, a mailslot. It was never ported to .NET, it is pretty useless. Broadcasting is not reliable, it is like yelling in a crowded football stadium without any guarantee that anybody can hear you. If you need broadcasts then you should consider an UDP socket. And of course deal with the consequence of it randomly losing data.

WCF is the usual recommendation if you consider named pipes. It puts a layer on top of them to make them easier to use.

Hans Passant
  • 922,412
  • 146
  • 1,693
  • 2,536
  • Sir, thanks for your reply. After reading few articles and searching on google. I came to a point that what i need to do is to create a mutex and different process can access that mutex. however i do not how can i achieve it through programming in c# . Is there any article or sample code can you share ? It will be very valuable for me. – shujaat siddiqui Feb 14 '14 at 14:55
  • That's another question, you can ask it (after searching) by clicking the Ask Question button again. – Hans Passant Feb 14 '14 at 14:57