Interprocess Communication problems
-
I have an application (Application A) which will launch another application (Application B) by passing some arguments in same machine. One of the argument is language use in Application A. When Application A run in Italian.lang, then Application B will launched in Italian.lang as well. Now, if Application A change language to English.lang, then running Application B need to change language to English as well. So i decide to use some inter-process communication method to solve this problem. I have limited time to do this changes. Application A will send notice to Application B when change language. Application B just need to listen to Application A. If possible i would like to have 2 way communication to adapt future change request. What method is suit with my project? Pipe or socket? Or any other method suit for it?
-
I have an application (Application A) which will launch another application (Application B) by passing some arguments in same machine. One of the argument is language use in Application A. When Application A run in Italian.lang, then Application B will launched in Italian.lang as well. Now, if Application A change language to English.lang, then running Application B need to change language to English as well. So i decide to use some inter-process communication method to solve this problem. I have limited time to do this changes. Application A will send notice to Application B when change language. Application B just need to listen to Application A. If possible i would like to have 2 way communication to adapt future change request. What method is suit with my project? Pipe or socket? Or any other method suit for it?
Go for sockets. Use
TCPListenerand do TCP communication.Navaneeth How to use google | Ask smart questions
-
Go for sockets. Use
TCPListenerand do TCP communication.Navaneeth How to use google | Ask smart questions
A quick suggestion here would be to use windows messaging. The SendMessage API in windows..But for this you need to know the windows handle..Since it is in a same machine .. this technique will be the easest and light weight way. than going for tcp http://www.codeproject.com/KB/dotnet/VB6andVBNETWindowMessages.aspx[^]
Shyam.. My Blog dotnetscoups.blogspot.com
modified on Friday, February 27, 2009 2:34 AM
-
Go for sockets. Use
TCPListenerand do TCP communication.Navaneeth How to use google | Ask smart questions
I would suggest a different approach, as it is obvious that TCP channels are wasteful when the two applications run on the same machine. There's an article I wrote which explains how to do IPC in C#. It's not the main purpose of the article, but you can use it to get ideas... It's called A Pure .NET Single Instancing Solution[^] Good luck... Shy.
-
I would suggest a different approach, as it is obvious that TCP channels are wasteful when the two applications run on the same machine. There's an article I wrote which explains how to do IPC in C#. It's not the main purpose of the article, but you can use it to get ideas... It's called A Pure .NET Single Instancing Solution[^] Good luck... Shy.
Thanks a lot. It is the best solution that i found. I will try on it later when i finish other feature.Thanks. Regards, PeiYang