Geek Answers Handbook

Best mechanism for implementing IPC bus in .NET?

I have several applications that want to communicate LOCALLY through the data bus.

Perfectly:

  • They talk and listen when they go online.
  • There will be no "owner" of this communication method.
  • No additional components to install (i.e. message queue)
  • It would be nice if there were no ports requiring open

What do you think is the best technology for this?

Is there a way to use WCF for the data bus?

0
source share
2 answers

Yes, and I can use WCF for this. Associating with a named pipe is amazing when using interprocess communication. It is easy to use (provided that you have access to services) and is very effective. I think this is consistent with what you are trying to do differently (from how you describe it).

There are many articles on the web about using this binding. Here - this is the one that aims at what you describe ... I read it a little, but your mileage with this particular one may differ.

If you are looking for WCF and Named Pipe, you will find many resources there.

+1
source

You can also take a look at this:

http://www.codeproject.com/KB/WCF/NullTransportForWCF.aspx

0
source

More articles:


All Articles