dcom vs com+ vs remoting

dotnet framework

    Sponsored Links


  • 1. Problem in the DMZ
    Hi I'm having problem with .Net Remoting when I invocate an Remote Object from the DMZ On the Intranet it works fine, but when I put the client on the DMZ, it doesn't work Is it the firewall that is blocking I get a HTTP 401 Error - UnAuthorized Acces Thank's in advance Goncalo
  • 2. Peer-to-peer
    Does anybody know where I can find a reference to build a peer-to-peer application with .NET Remoting (in C#)?
  • 3. proxying an object for intersept methods call
    Im just using my proxy implementation using .Net Remoting ,but for proxy an object I must declare an interface(s) with all the method that I want to intercept calls an the target object must implement it. I try to do it without implement the interface(s) with attributes in all methods that I want to intercept calls, but if the class where are the methods doesnt implement any interface I receive a transparentProxy instead an object that I expect when I create my Proxy Thanks for any help
  • 4. Remote on remote
    I am trying to host a remote object that consumes another remoted object I am using the RemotingConfiguration.Configure method to setup both configurations and while the first remoting setup succeeds the second one fails. I get no entries from the WellKnownClientTypeEntry method so it seems that the RegisterWellKnownClientType-part of the automatic configuration fails I reckon that I could successfully manage to setup both my configurations programmatically if there was a way to get hold of the remoted objects type "Type.GetType(string)" without referencing the assembly So * Should it be possible to setup both configurations using configuration files * Is there a way to get hold of the Type without a reference to the remoted assembly (one does not need that if using configuration files).
  • 5. Performance question
    I'd like to know what those who have tested the following think performance wise - remotin - serializing the object and sending it directly to the serve Which one is faster if there's one I understand that things will be very different depending on the object passed - so let's say for an object with an x and a y variable (for serialization use), and a SetCoords(x, y) method (for remoting use) I did some testing and found to my surprise that remoting was faster on the same machine, but things were completely different when the client was on another computer. Also, if I include response from the server in the serialization mechanism, performance starts dropping dramatically. Does anyone have experience with this ? I'd love to hear about this.

dcom vs com+ vs remoting

Postby BK Kim » Fri, 06 Feb 2004 10:40:19 GMT


I am doing a research on dcom, com+ and remoting.

We are about to develop a web application consisting 3 tiers ( web server,
application server, db server )

We are going to develop front end in asp.net and ms sql in the back end.

The middle tier mostly will be grabbing data from the db and give the result
to the front end.

I'd like to know what would be the better way to do this.

Should I use only one object in the middle tier that communicate to all the
threads requested from the web server? ( i'd like to know the pres and
cons )

I heard that dcom is better than com+ in particular situation so I'd like to
know in what situation remoting would be the best fit in the middle tier and

Thanx in advance

Re: dcom vs com+ vs remoting

Postby Thomas Tomiczek [MVP] » Fri, 06 Feb 2004 16:57:21 GMT

Use neither, but drop the DAL into the webserver.


Yes, if you do not care about performance.


Thomas Tomiczek
THONA Software & Consulting Ltd.
(Microsoft MVP C#/.NET)
(CTO PowerNodes Ltd.)

Still waiting for ObjectSpaces? Try the EntityBroker today - more versatile,
more powerfull.
And something in use NOW. for the projects you have to deliver - NOW.


Re: dcom vs com+ vs remoting

Postby Allen Anderson » Sat, 07 Feb 2004 02:17:20 GMT

Avoid dcom like the plague (which it is).  However, the decision
between com+ and remoting is a more difficult one as com+ will
probably give you better performance and remoting will be easier to
implement/maintain (which can be a real issue if you intend to heavily
cluster your web and business logic tiers).  Also you need to decide
if you are good with a mixed solution of .net and legacy approaches if
you go com+.  Overall though there are a lot of things to take into
consideration when making this decision.

Allen Anderson
mailto: allen@put my website url here.com

On Wed, 4 Feb 2004 17:40:19 -0800, "BK Kim" < XXXX@XXXXX.COM >

Re: dcom vs com+ vs remoting

Postby Ice » Sun, 08 Feb 2004 01:17:27 GMT

why do you say com+ (which is remoting over dcom) will give better



Re: dcom vs com+ vs remoting

Postby Allen Anderson » Sun, 08 Feb 2004 04:50:56 GMT

Well, beyond the fact that I've used both and com+ seems to be able to
scale much faster and higher than remoting (I've used both quite a
bit), I'm not otherwise aware of how they share infrastructure at all.
Maybe you know something I don't in this?

Allen Anderson
mailto: allen@put my website url here.com

Re: dcom vs com+ vs remoting

Postby Ice » Tue, 10 Feb 2004 22:58:31 GMT

ell maybe we are talking about 2 different things.
obviously there is communication between client and server and this can
impacted by your host.
what i'm saying is that if you com+ and create application proxies, then
communication is still DCOM wrapped with Remoting hence why all your
expections are remoting exceptions - all the rules apply.
COM+ as a host can incur performance penalties if not configured correctly,
otherwise its roughly the same as using a Windows Service.

I am curious however about your scalability point. Can you elaborate on
this a bit?


"Allen Anderson" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...

Similar Threads:

1.COM+ vs .Net Remoting vs...

Good day!

I don't remember where I saw caomparision of COM+ and .NET remoting and 
guidelines for these techonologies usage. If anyone can help me to find these 
links - please, do it.
But now I have on eproblem:
THere are client application which must be written on C++, server 
application written on .NET, and with capability to use COM plugins, plus 
there is have to be realizaed capability to use application server without 
metwork access (direct usage of core part, business logic).
Moreover in near future may be decided to move all server to the cluster 
with self-written load balancing system.

Now I have the following ideas:
Client on C++ using TCP/IP connects with server.
There is windows service on the server (written on .NET) which serves 
queries from client and redirects all these queries for processing to COM+ 
component (server). This COM+ compenent accesses DB, process data etc.

And here is a question: what is better than COM+?
What are the advantages of COM+, of .NET Remoting in this case?
What other (or this modified) approaches could me used?
WHat I must to use to easily create clustered application?

And, one more question: Is it possible to work with COM+ from unmanaged code?
It seems, yes, but my senile brain don't want to remember right answer.

A lot of Thanks

2..NET Remoting vs. DCOM

Hi All,
I have a .NET serviced component as an Application Server between the
web server(asp.net) and the database.
There is a COM component registered on the web server for legacy
operations and as a part of that it makes DCOM calls to the
Application Server.
I have a requirement where my aspx.cs needs to call the Application
Server and I was wondering if I should use Remoting to achieve this or
simply forward the call to my registered component (which would use
DCOM). My requirement would fall into the category of SAO, SingleCall.
Are there any perf nos. comparing DCOM & .Net Remoting.


3.Remoting Vs. DCOM

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


4.Enterprice Services (via DCOM) vs IIS (via Remoting) for high volume apps

5.Com+ vs IIS vs StandAlone

As im sure most of you are aware of you can not host .Net services without 
IIS. This where my question comes in on what is the best practice on objects 
that you know will have to scale. With my understanding of .Net, if you host 
the process directly from a service, then every hit to the object is going 
to create a new object.. So if your getting 100,000 hits per minute (i know 
this is high but im using it as an example) then there will be 100,000 
objects created and destroyed. I assuming if i didn't work like this then it 
would be like apartment threading and only one call could happen at a time 
and there would be blocking. A lot of these objects will be in memory at the 
same time. Is my understanding of how things work lax or is this really is 
what going to happen? I would assume this would scale really poorly. This 
example could be a web service or say something you exposed with WCF.

My understanding of how IIS works is very limited. I'm sure that IIS has 
some time of redudancy threading to help the situation above. Am i right or 
am i wrong? So if you host under IIS would it scale any better?

Last comes com+. Which has facilities like object pooling & connection 
pooling and ect that i would think would allow these services to scale the 
best. Am i wrong?

So i guess the overall question is what is the differences between how each 
of these solutions would scale?  Which solution would be the best? Would 
there big a big difference

For simplicity lets leave server farms and clustering out of this.

Any help would be appreciated.


6. Windows-service remoting - IPC vs. COM

7. Remoting vs. COM GetObject()

8. remoting vs com

Return to dotnet framework


Who is online

Users browsing this forum: No registered users and 94 guest