Distributed Component Object Model
Software for communication between software components
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.
Nº Q906328 ★
Common · Literature
Distributed Component Object Model
Software for communication between software components
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.
Last price
—
Floor price
—
7-day median
—
30-day sales
0
30-day range
—
In circulation
0
Price history
median
low – high
sales
No sales in this period
Show table
| Date | median | Low | High | sales |
|---|
Sales history
- Last sale
- —
- 30-day average
- —
- 30-day low
- —
- 30-day high
- —
- Sales 7d
- 0
- Sales 30d
- 0
No sales yet.
Anonymous sales: no buyer or seller shown. Figures count player-to-player sales only.
From Wikipedia
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: 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...
Text: Wikipédia, CC BY-SA 4.0. ·
Related cards
Component Object Model
Application Binary Interface by Microsoft
Nº Q662200 ★★
Dynamic Data Exchange
Inter-process communication protocol on Microsoft Windows
Nº Q1268873 ★
Object Linking and Embedding
Technology developed by Microsoft
Nº Q848314 ★
Remote procedure call
Mechanism to allow software to execute a remote procedure
Nº Q62270 ★★★
Digital Command Control
System for digital control of model railways
Nº Q905329 ★★
ActiveX Data Objects
Component Object Model APIs for accessing data sources
Nº Q344005 ★★★