ASP.NET Web Services and .NET Remoting
1.Protocol
Can be accessed only over HTTP
Can be accessed over any protocol (including TCP, HTTP, SMTP and so on)
2.State Management
Web services work in a stateless environment
Provide support for both stateful and stateless environments through Singleton and SingleCall objects
3.Type System
Web services support only the datatypes defined in the XSD type system, limiting the number of objects that can be serialized.
Using binary communication, .NET Remoting can provide support for rich type system
4.Interoperability
Web services support interoperability across platforms, and are ideal for heterogeneous environments.
.NET remoting requires the client be built using .NET, enforcing homogenous environment.
5.Reliability
Highly reliable due to the fact that Web services are always hosted in IIS
Can also take advantage of IIS for fault isolation. If IIS is not used, application needs to provide plumbing for ensuring the reliability of the application.
6.Extensibility
Provides extensibility by allowing us to intercept the SOAP messages during the serialization and deserialization stages.
Very extensible by allowing us to customize the different components of the .NET remoting framework.
7.Ease-of-Programming
Easy-to-create and deploy.
Complex to program.
difference ASP.NET Web Services and .NET Remoting
Labels: Remoting
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment