remoting vs com

  • Thread starter Thread starter Sharon
  • Start date Start date
S

Sharon

hi all.
i don't know much about com or .net remoting so this question might be a
little confused.
as far as i understand com system provides about the same functionality as
ejb
meaning that it has to have some kind of container.
an application server like jboss in the case of ejb.
in .net remoting i can register my service classes without the need for an
application server.
so is there any advantage to using com / application server?
when you'll have to build a distributed application which method will you
choose?
is com going to become legacy?
10x much.
 
Sharon said:
hi all.
i don't know much about com or .net remoting so this question might be a
little confused.
as far as i understand com system provides about the same functionality as
ejb
meaning that it has to have some kind of container.
an application server like jboss in the case of ejb.
in .net remoting i can register my service classes without the need for an
application server.
so is there any advantage to using com / application server?
when you'll have to build a distributed application which method will you
choose?
is com going to become legacy?
Click to expand...

COM (nee ActiveX, nee OLE) = Component Object Model

COM+ (nee MTS, aka Component Services, aka Enterprise Services) =
Application Server

COM is definitily on the way out. COM+ is not.

COM+ offers a range of services for running your service classes. (Lifetime
Services, Queued Components, Object Pooling, Contexts etc). You can use
these or do without quite easilly. For instance COM+ allows you to drop in
a service class and run it as a service. You can also just write a service,
open a remoting channel, and you've got your own application server.

David
 
This might be a bit offbeat.
I have used COM with VB, but not COM+ much. I heard that COM+ server does
not provide object pooling although the UI has the facility to set the
object pool size! Is this true?

Krishnan
 
Sharon said:
got it .
10x :)
one more question:
is com+ replacing dcom as well?
Click to expand...

DCOM is the remoting protocol for COM.
COM+ uses DCOM for remoting COM objects.

So as COM components are replaced by .NET assemblies, DCOM is replaced by
..NET remoting.

David
 
10x again for moving things into place :)

David Browne said:
DCOM is the remoting protocol for COM.
COM+ uses DCOM for remoting COM objects.

So as COM components are replaced by .NET assemblies, DCOM is replaced by
.NET remoting.

David
Click to expand...
 
Back
Top