Web Services vs .NET Remoting over HTTP with SOAP

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Samuel R. Neff - 15 Jun 2007 02:57 GMT

What are the differences between using web services and using .NET
remoting with http transport and soap encoding ?

When dealing with .net to .net communications, particular when the
same company is responsible for both sides of the app (client and
server), what are advantages/disadvantages of each?

Thanks,

Sam

------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.

Reply to this Message

Aidy - 15 Jun 2007 09:44 GMT

One advantage of web services is dynamic discovery.

> What are the differences between using web services and using .NET
> remoting with http transport and soap encoding ?
[quoted text clipped - 12 lines]
> development in MD/DC. Work with a variety of technologies
> in a relaxed team environment. See ads on Dice.com.

Reply to this Message

John Saunders [MVP] - 15 Jun 2007 12:35 GMT

> What are the differences between using web services and using .NET
> remoting with http transport and soap encoding ?
>
> When dealing with .net to .net communications, particular when the
> same company is responsible for both sides of the app (client and
> server), what are advantages/disadvantages of each?

Web services are meant to be platform-neutral. That means least common
denominator.

With .NET remoting, you can use .NET-specific features like properties,
indexers, and even non-default constructors.

Signature

John Saunders [MVP]

Reply to this Message

Web Services vs .NET Remoting over HTTP with SOAP

Free Magazines