Distributed Component Object Model

Also found in: Acronyms, Wikipedia.

Distributed Component Object Model

(DCOM) Microsoft's extension of their Component Object Model (COM) to support objects distributed across a network. DCOM has been submitted to the IETF as a draft standard. Since 1996, it has been part of Windows NT and is also available for Windows 95.

Unlike CORBA, which runs on many operating systems, DCOM is currently (Dec 1997) only implemented by Microsoft for Microsoft Windows and by Software AG, under the name "EntireX", for Unix and IBM mainframes. DCOM serves the same purpose as IBM's DSOM protocol.

DCOM is broken because it's an object model that has no provisions for inheritance, one of the major reasons for object oriented programming in the first place.


This article is provided by FOLDOC - Free Online Dictionary of Computing (foldoc.org)
Mentioned in ?
References in periodicals archive ?
There have been previous attempts to solve this unique problem by seamlessly connecting distributed applications using technologies like common object request broker architecture (CORBA) and and distributed component object model (DCOM), but none of these technologies have turned out to be a panacea.
RAO of the kernel is basically middleware that provides a unified access method to robot data, based on Distributed Component Object Model (DCOM) technology.
Well-known distributed technologies using proprietary protocol are DCOM (Microsoft's Distributed Component Object Model), CORBA and Java RMI.
The most common are the Common Object Request Broker Architecture (CORBA) and the Distributed Component Object Model (DCOM).
The two vulnerabilities are in the components of Windows that deal with remote procedure calls (RPC) to distributed component object model (DCOM) services.

Full browser ?