Inter process communication

  • Thread starter Thread starter Steve B.
  • Start date Start date
S

Steve B.

Hi,

I'd like to know what is the most efficient way to make two processes speak
each others on the same, or several computers.

Is remoting built for that ?

Thanks,
Steve
 
I'd like to know what is the most efficient way to make two processes
speak each others on the same, or several computers.
Click to expand...
That's a vast question....
There is multiple articles on that in the SDK documentation and in the MSDN
library
Look for:
Remoting, Web Services, XML-RPC, RPC, Indigo, Socket messaging,
communication protocol, SOAP messaging, Corba, ....

Is remoting built for that ?
Click to expand...
Yep, remoting is one solution.
It's the most performant but suffers from tight coupling.

Thanks,
Click to expand...
you're wellcome
 
I'd like to know what is the most efficient way to make two processes
speak each others on the same, or several computers.

Is remoting built for that ?
Click to expand...

It is, but we've heard Microsoft speakers at TechEd say "don't use remoting".
It can get ugly if you're not careful and don't follow the proper rules.

But, it's the quickest and easiest method, which is partly why it can be
dangerous. If your use is limited and easy to support problems (like in-house
rather than complicated solution deployed by end-customers) and doesn't need
long term compatability, go for it.
 
My goal is to have an windows service running on the clients computer
(intranet scenario). This service must perofrm some tasks that the user can
control from its desktop. That's why I'm looking for a way to make the
server (the windows service) and the client (a user application) communicate
each others, even if it is on the same computer.

I'm also thinking of a future release of the application. This release will
include a "central" administration console for an administrator.

You talk about possible dangers of the remoting. Could you tell me more ?

Thanks in advance,
Steve


"Eric Pearson" <http://blog.ericpearson.org
http://www.geekswithblogs.com/ericpearson> a écrit dans le message de (e-mail address removed)...
 
If you clients will all be .Net and your server(s), then go for it.
Remoting is still a great way to go. Also, you could check out WCF (i.e.
Indigo).

--
William Stacey [MVP]

| My goal is to have an windows service running on the clients computer
| (intranet scenario). This service must perofrm some tasks that the user
can
| control from its desktop. That's why I'm looking for a way to make the
| server (the windows service) and the client (a user application)
communicate
| each others, even if it is on the same computer.
|
| I'm also thinking of a future release of the application. This release
will
| include a "central" administration console for an administrator.
|
| You talk about possible dangers of the remoting. Could you tell me more ?
|
| Thanks in advance,
| Steve
|
|
| "Eric Pearson" <http://blog.ericpearson.org
| http://www.geekswithblogs.com/ericpearson> a écrit dans le message de
| (e-mail address removed)...
| >> I'd like to know what is the most efficient way to make two processes
| >> speak each others on the same, or several computers.
| >>
| >> Is remoting built for that ?
| >
| > It is, but we've heard Microsoft speakers at TechEd say "don't use
| > remoting". It can get ugly if you're not careful and don't follow the
| > proper rules.
| > But, it's the quickest and easiest method, which is partly why it can be
| > dangerous. If your use is limited and easy to support problems (like
| > in-house rather than complicated solution deployed by end-customers) and
| > doesn't need long term compatability, go for it.
| >
| >
| >> Thanks,
| >> Steve
| >
| >
|
|
 
Back
Top