First off, you need to understand what terms to use. If you are not doing
this for homework, and want to dive deep here, look at the patterns
described in this excellent book:
Enterprise Integration Patterns by Hohpe and Woolf
http://www.eaipatterns.com/
..Net is not based on COM+. A .Net app is free to use COM+ if it so
chooses... or not.
As far as RPC mechanisms, you can look into XML Web Services as well as .Net
Remoting. Windows Communications Foundation (Indigo) introduces an elegant
and configurable layer to handle RPC and some messaging (Queues and
EndPoints mostly) that will make EAI much more configurable.
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
<ap****@yahoo.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
When an application needs to get information from another machine over
the network, how many distributed computing choices out there?
Here are the choices in microsoft technology:
.NET is based on COM+, or what underlying technology it is using for
distributed communication?
HTTP (any??)
.NET (Microsoft)
COM+ (Microsoft)
SOAP (any ??)
MOM (any ??)
I guess HTTP is just the protocol, it should not belong to the
distributed computing choices?
Please comment and advise. thanks!!