Distributed Component Object Model

Distributed Component Object Model (DCOM) is a proprietary Microsoft technology for communication between software components on networked computers. DCOM, which originally was called "Network OLE", extends Microsoft's COM, and provides the communication substrate under Microsoft's COM+ application server infrastructure. The extension COM into Distributed COM was due to extensive use of DCE/RPC (Distributed Computing Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known as MSRPC. In terms of the extensions it added to COM, DCOM had to solve the problems of:

Comment
enDistributed Component Object Model (DCOM) is a proprietary Microsoft technology for communication between software components on networked computers. DCOM, which originally was called "Network OLE", extends Microsoft's COM, and provides the communication substrate under Microsoft's COM+ application server infrastructure. The extension COM into Distributed COM was due to extensive use of DCE/RPC (Distributed Computing Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known as MSRPC. In terms of the extensions it added to COM, DCOM had to solve the problems of:
Date
13 January 2020
Has abstract
enDistributed Component Object Model (DCOM) is a proprietary Microsoft technology for communication between software components on networked computers. DCOM, which originally was called "Network OLE", extends Microsoft's COM, and provides the communication substrate under Microsoft's COM+ application server infrastructure. The extension COM into Distributed COM was due to extensive use of DCE/RPC (Distributed Computing Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known as MSRPC. In terms of the extensions it added to COM, DCOM had to solve the problems of: * Marshalling – serializing and deserializing the arguments and return values of method calls "over the wire". * Distributed garbage collection – ensuring that references held by clients of interfaces are released when, for example, the client process crashed, or the network connection was lost. * Combining significant numbers of objects in the client's browser into a single transmission in order to minimize bandwidth utilization. One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory. DCOM was a major competitor to CORBA. Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the Internet. However, the difficulties involved in getting either of these technologies to work over Internet firewalls, and on unknown and insecure machines, meant that normal HTTP requests in combination with web browsers won out over both of them. Microsoft, at one point, attempted to remediate these shortcomings by adding an extra http transport to DCE/RPC called ncacn_http (Network Computing Architecture connection-oriented protocol). DCOM was publicly launched as a beta for Windows 95 September 18, 1996. DCOM is supported natively in all versions of Windows starting from Windows 95, and all versions of Windows Server since Windows NT 4.0
Hypernym
Technology
Is primary topic of
Distributed Component Object Model
Label
enDistributed Component Object Model
Link from a Wikipage to an external page
opengroup.org/comsource
web.archive.org/web/20200113034910/http:/opengroup.org/comsource
tools.ietf.org/html/draft-brown-dcom-v1-spec-03
web.archive.org/web/20091213022641/http:/tcom.andjoin.com/
Link from a Wikipage to another Wikipage
.NET Remoting
ActiveX
Category:Component-based software engineering
Category:Inter-process communication
Category:Object models
Category:Object request broker
Category:Windows communication and services
Client–server model
Component Object Model
Computer
CORBA
Digital Unix
Dynamic Data Exchange
Firewall (networking)
Garbage collection (computer science)
HTTP
Internet
Marshalling (computer science)
Microsoft
MSRPC
NTLM
Object Linking and Embedding
OLE for process control
Persistence layer
Proprietary software
RPC
Software componentry
Web browser
Win32
Windows NT
Windows Registry
SameAs
541eS
Dağıtılmış Bileşen Nesne Modeli
DCOM
DCOM
Distributed COM
Distributed component object model
Distributed Component Object Model
Distributed Component Object Model
Distributed Component Object Model
Distributed Component Object Model
Distributed Component Object Model
Distributed Component Object Model
Distributed Component Object Model
Distributed Component Object Model
m.0n5vd
Modelo de Objetos de Componentes Distribuidos
Q906328
분산 컴포넌트 오브젝트 모델
Subject
Category:Component-based software engineering
Category:Inter-process communication
Category:Object models
Category:Object request broker
Category:Windows communication and services
Url
comsource
WasDerivedFrom
Distributed Component Object Model?oldid=1118146960&ns=0
WikiPageLength
8637
Wikipage page ID
93492
Wikipage revision ID
1118146960
WikiPageUsesTemplate
Template:Authority control
Template:Microsoft APIs
Template:Microsoft Windows components
Template:Redirect
Template:Reflist
Template:Short description
Template:Webarchive