1) Protocol : Webservice can be accessed over HTTP protocol . Remoting can be accessed over any protocol (including TCP, HTTP, SMTP etc)
2) Interoperability : Webservices support interoperability across platforms, and are ideal for heterogeneous environments. Remoting requires the client be built using .NET, enforcing homogenous environment.
3) Ease of programming : Webservice is easy to create and deploy . Remoting is complex to create
4) State Management : Webservices are stateless . Remoting support for both stateful and stateless environments through Singleton and SingleCall objects
Subscribe to:
Post Comments (Atom)
Popular Posts
-
Cache Callback provides an ability where by some actions can be performed when that item is removed from cache CacheItemRemovedCallback ex...
-
XML DOM loads the entire xml document into memory whereas Simple API for XML ( SAX ) does not load entire xml document into memory XML DOM ...
-
Different types of diagrams in UML : UseCase diagram Class diagram Object diagram State diagram Sequence diagram Collaboration diagram...
-
Virtual-Override and New Class Child inherits from Class Parent and has mehtod ShowVirtualOverride() and ShowNew() methods. Please see th...
-
Question : Name few C# 3.0 enhancements ? Answer : The C# 3.0 language enhancements are as follows: Implicitly typed local variables I...
-
If locaction attribute is specified, must be one of: Any, Client, Downstream, None, Server or ServerAndClient.
Posts
No comments:
Post a Comment