Groups | Blog | Home
all groups > dotnet remoting > august 2005 >

dotnet remoting : Why would I NOT use remoting?


Michael
8/16/2005 11:46:57 AM
I'm wring a smart client app which will be used 90% within a LAN and 10%
across the Internet though the Internet use may increase over time. I've set
off using remoting but have noticed Microsoft suggesting in a number of
places that we should use Web Services in preference most of the time and
also today this :-

http://www.theserverside.net/articles/showarticle.tss?id=PickingSmartClient

I'm using .NET 2.0 for both client and server. Security across the Internet
is v.important and performace within the Lan is v.important.

I can't quite see why Web Services is pushed so strongly. Why would I not
use remoting?

Nicolas Bouchard
8/17/2005 6:05:47 AM
I guess WebServices will be supported widely and without any problem
with firewalls. Remoting may have some problem with firewall depending
on how you setup them. I know that if you use binary serialization, you
may have trouble with internet connections. But I guess if you use IIS
and HTTP protocol, you won't have to bother with firewalls.

I have little experience with web services, but I found out, they were
easy to develop, really easy to use; but the serialization used by them
can be slower than a TCP/Binary remote object. But you'll have the same
problem with a HTTP/Text remote object.
nobody
8/17/2005 9:55:19 AM
Web service has the following advantages.
1. Simple to develop with high level development languages like C#,
VB.Net, Java, etc.
2. Great interoperability among all of major development languages
(C++, Java, DotNet etc).
3. No firewall problems.

Web service also has the following disadvantages.
1. Slowest and largest overhead protocol among the world among all
known remoting frameworks like Java RMI, DCOM, Corba, Socket.
2. Features are limited. Many features are NOT available to web
service.



[quoted text, click to view]

AddThis Social Bookmark Button