Discussion Locked

.NET Remoting vs .NET Web Services

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Ok... I've successfully built and tested .NET Web Services, and think I have a pretty good handle on them. Now I am grappling with .NET Remoting, a vastly more complex topic, and having a little trouble understanding how the end result is differentfrom Web Services (and what the payoff is for all of the extra work).

In other words, while .NET Remoting is vastly less complicated than what one had to go through in the past in order to achieve inter-application-domain communications... with the advent of .NET XML Web Services (very cool, very simple to develop and implement), why do I need .NET Remoting?

If the answer to this question is obvious, please forgive my ignorance... I would welcome a bit of enlightenment.

3 replies

by herbert.kern

... though remoting and web services do have many things in common.

1.) Web services lack the concept of state, Remoting objects do have a state.
2.) With remoting you are not bound to tcp/ip or http as protocol for communication
3.) With remoting you can choose where to host the remotable object: IIS or your own server(-process)
4.) Remoting supports the concept of client vs. server activated objects.
5.) You can access .net web services also from java or python

by |_|di

It all boils down to this:

If interoperability with diverse systems is your primary goal, then web services is the route.

If performance is your primary goal, and you will be communicating between systems of the same platform ( ie MS ) and you're not afraid to code, then Remoting is the preferred route.

Hope that helps.

by riggsfolly

I heard this from a Trainer @ Learning Tree last week so it is second hand.

He basically said that within Microsoft there was 1 guy looking after the .NET Remoting technology and of course a major team for the Web Services technologies. If you report problems in the WS area people bustle about to get a solution while with Remoting solutions are much slower. While this isn't necessarily a good reason for selecting a technology ignore it at your peril.

This discussion is closed to new replies.