Protocol
[Web services] - Can be accessed only over HTTP
[.NET remoting] - Can be accessed over any protocols (including TCP, HTTP, SMTP, etc.)
State Management
[Web services] - Web servcies work in a stateless environment
[.NET remoting] - Provide support for both stateless and stateful environmentts through Singleton and SingleCall objects
Type System
[Web services] - Web services support only the datatypes defined in the XSD type system, limiting the number of objects taht can be serialized
[.NET remoting] - Using binary communication, .NET remoting can provide support for rich type system
Interoperability
[Web services] - Web services support interoperability across platforms, and are ideal for heterogeneous environements
[.NET remoting] - .NET remoting requires teh client be built using .NET, enforcing homogenous environment
Reliability
[Web services] - Highly reliable due to the fact that web services are alaways hosted in IIS
[.NET remoting] - Can also take advantage of IIS for fault isolation. If IIS is not used, application needs to provide plumbing for ensuring the reliablity of the application.
Extensibility
[Web services] - Provides exntensibility by allowing us to inbtercept the SOAP messages during the serialization and deserialization stages
[.NET remoting] - Very extensive by aloowing us to customize the different components of the .NET remoting framework.
Ease-of-Programming
[Web services] - Easy to create and deploy
[.NET remoting] - Complex to program
** So when to use them?
Use web Services when you need need to send and receive data from different computing platforms, use .NET remoting when sending and rceiving data between .NET applciaitons. Although in some architectural scenario, you can use both.
CodeWizard posted on Nov 09, 2006
| views: 93
