I have two processes running on the same windows machine. One is using mono, the other is using MS .NET.
What is the best solution for inter process communication?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have two processes running on the same windows machine. One is using mono, the other is using MS .NET.
What is the best solution for inter process communication?
Really, I would say you need to provide more information for a good answer. The type of IPC depends on your needs. I’ve used several types of IPC, shared memory, files, memory mapped files, pipes, sockets, etc. I think this question is less about .Net vs. Mono and more about you specific needs.
That said, I’ve used mostly TCP and UDP for most of my applications. The VM, language, computer, etc. become irrelevant when you put your communications over the network. For local communications your loopback device (127.0.0.1) works great. If you ever decide to take your application to another machine, you only need to change addresses.
Put your data (e.g. http in an existing protocol and you’ll get out-of-the-box from most languages…