Fog Creek Software
Discussion Board

Welcome! and rules

Joel on Software

,NET Remoting vs. web services

The other post on web services got me thinking:  What's the practical application of .Net remoting versus a web service.  ie when would it be better to use one over the other?

I understand (mostly) the technical difference between the two, and have built both as one-off exercises at work.  And both accomplished the same end (talked to another machine to run a thrid party app installed only on that machine).  So, in the real world what's my criteria for deciding which to use?

Just wondering if any one had practical experiences to share or other advice.


Friday, July 30, 2004

As it is:
.Net Remoting is good when you control both sides of the equation and both sides are .Net based, and web services are better when you've got control on one end, accepting information from any number of partially/totally unknown sources (.Net or otherwise).

As it shall be:
.Net Remoting will go by the wayside as the ASMXy codename-Indigo interoperability object model is introduced.  Web services will remain, boosted by the WSE2 usage.

Outside of that, you've probably got a good taste of the pluses and minuses of each - I'd stick with Web Services, personally.

Greg Hurlman
Friday, July 30, 2004

Remoting also has performance advantages, at least in part because it can use a binary wire format, rather than converting everything to XML and adding all the tags, etc.

Monday, August 2, 2004

You may find the comments here useful:

John Rusk
Friday, August 6, 2004

See also:

John Rusk
Sunday, August 29, 2004

*  Recent Topics

*  Fog Creek Home