Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / August 2005

Tip: Looking for answers? Try searching our database.

Remoting Vs. DCOM

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ram - 15 Aug 2005 08:50 GMT
Hey,
If I don't need to worry about security, but performance is a big
issue, should I use Remoting or EnterpriseServices with DCOM to connect
my clients to my server?
Besides performance, what other advantages/disadvantages are there for
each of them, and what about Indigo?
Thanks ahead

Ram
hB - 15 Aug 2005 11:10 GMT
It depends what type of communication you want to achieve between
server and the clients.

If... (in general)
Its better to do Remoting with RAW TCP/IP binary streams, it will be
best solution performance wise in the dotnet.
(there could be nothing faster than direct sockets and binary streams
(udp even more, but no streams))

For adv/disadv:
http://www.theserverside.net/discussions/thread.tss?thread_id=35073
http://groups.google.ae/group/microsoft.public.dotnet.framework.remoting/browse_
thread/thread/fc2bb42359bfaaee/73dab004adb8c51f?lnk=st&q=COM%2B+Web+Services+Rem
oting&rnum=1#73dab004adb8c51f

http://groups.google.ae/group/microsoft.public.dotnet.framework.remoting/browse_
thread/thread/660563546cc7868e/c781e2faa9f0ced0?lnk=st&q=COM%2B+Web+Services+Rem
oting&rnum=5#c781e2faa9f0ced0


type "COM+ Web Services Remoting" in groups.google.com :)

---
hB
Cowboy (Gregory A. Beamer) - MVP - 15 Aug 2005 13:37 GMT
DCOM might (the key word is MIGHT, not WILL) work a bit faster with very
small messages. Beyond that, the extra layers on both sides of the
communication will bog it down. For that reason, I would head towards
Remoting first.

All of the upcoming technologies are XML based, so they are more akin to
Remoting than DCOM.

Signature

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

> Hey,
> If I don't need to worry about security, but performance is a big
[quoted text clipped - 5 lines]
>
> Ram
Ram - 16 Aug 2005 18:58 GMT
Thanks for both of your replies!
Gregory - XML based technologies/protocols are all fine and sexy, but
when talking about performance, they are a lot behind (and will always
be???) DCOM/Remoting - binary based technologies...
My application will be transferring big chunks of data and must have
high performance - so XML based technologies i.e Web Services are out
of question...
Bottom line, even though .Net Remoting is managed and is closed to
Indigo, DCOM offers me more standard and reliable framework, with built
in monitoring (the Com+ MMC), better performance (like you said) and of
the little I read about .Net Remoting, I understand that it is'nt 100%
managed as well, and the path from V1.1 Remoting to Indigo is not as
clean as other technologies (EnterpriseServices???) so I might as well
stick to what technology right now is more comfortable...
Please tell me what you think, and again thanks for replying!

Ram

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.