Professional Touch International Inc.   
About Us   Home   Questionnaire    Shopping Cart    Your Account    Help   

Login
(954) 430-5263 
Contact Us

Product Categories
Windows Applications
Web Applications
Web Services
Web Pages
Web Controls
Smart Windows Applications
SQL Tables
SQL Views
SQL Stored Procedures
SQL User Defined Functions
N-Tier Classes
Hosted Solutions
Windows Services
Smart Clients
Windows Techniques
ASP.NET Techniques
Miscellaneous Techniques
Pre-Packaged Solutions
ASP.NET List Control
Consulting Hours
Remoting
Dynamic Documentation
Deployment
One-Time Fees
On-Going Fees
 
Other Site Pages
Products
Smart Applications
Synergy Ingredients
Web Services vs Remote
FAQs
Revolutionary Concepts
MMIT vs SDE
Dynamic Graphs
Dynamic Documentation

To Web Service or To Remote

Web Services and Remoting are distinct technologies with a different set of goals and features. If you're looking for interoperability, ASP.NET web services are ideal, if you need to communicate between two .NET centric applications, nothing is better than .NET Remoting. 

.NET Remoting is a technology designed to allow .NET applications to talk to each other, whether they are on the same machine or on different machines, across a network, or even the Internet. Remoting is substantially more flexible and powerful than XML Web services, but doesn't necessarily conform to any open standard, such as SOAP.

Web services provide a standards-based, open communication medium that is the obvious choice for sending and receiving data between different computing platforms and programming languages. Remoting is more proprietary to .NET, but is also faster and more flexible, and is often the best choice for sending and receiving data between .NET applications.

Web Services are not always the ideal solution to any client/server requirement. Sometimes they don't provide the performance or capabilities we require and we're left looking for a more appropriate alternative. Remoting is sometimes a more appropriate client/server technology because it offers better performance and more capabilities than Web services.

The following table helps cross reference Web Services features with those found in Remoting.

 

Capability Web services Remoting
Invoke single method on a stateless object Yes Yes
Invoke multiple methods on a stateful object  No Yes
Have all clients invoke methods on the same server-side object  No Yes
Pass through firewalls Yes Yes
Uses HTTP for communication Yes Yes
Uses raw TCP socket for communication No Yes
Use IIS as host Yes Yes
Allow custom host No Yes
Uses SOAP-compliant formatting of data Yes Yes
.Uses smaller binary formatting of data No Yes
Retrieve partial copy of data from complex object Yes Yes
Retrieve complete copy of complex object No Yes

 

Table highlights the differences in capabilities between the two technologies. Rockford Lhotka - Magenic Technologies - October 23, 2001To read entire document .To read entire document Click Here

 

Additional resources

Dino Esposito, one of our favorite instructors, explains .NET Remoting in his October 2002 MSDN Magazine article titled "Design and Develop Seamless Distributed apps for the CLR". To view the article Click Here

.NET Framework Samples: Remoting Basic

.NET Framework Samples: Remoting Advanced

Microsoft .NET Remoting: A Technical Overview

.NET Remoting Overview 

©2002 Professional Touch International, Inc.

This is a dynamic ASP.Net page. It was created at: 3/10/2010 12:30:01 AM