Distributed Component Object Model

Distributed Component Object Model (DCOM) is a proprietary Microsoft technology for communication among software components distributed across 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. It has been deprecated in favor of the Microsoft .NET Remoting, a part of their .NET Framework.

The addition of the "D" to 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.
  • Aggregating hundreds or potentially tens of thousands of references to objects held by clients of interfaces at a single host, into a single "ping" function, in order to minimise bandwidth utilisation.

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 and failed to head this off by adding an extra http transport to DCE/RPC called ncacn_http (Network Computing Architecture, Connection-based, over HTTP). This was later resurrected to support a Microsoft Exchange 2003 connection over HTTP.

Read more about Distributed Component Object Model:  Alternative Versions and Implementations, Procedure

Famous quotes containing the words distributed, component, object and/or model:

    Indiana was really, I suppose, a Democratic State. It has always been put down in the book as a state that might be carried by a close and careful and perfect organization and a great deal of—[from audience: “soap”Ma reference to purchased votes, the word being followed by laughter].
    I see reporters here, and therefore I will simply say that everybody showed a great deal of interest in the occasion, and distributed tracts and political documents all through the country.
    Chester A. Arthur (1829–1886)

    ... no one knows anything about a strike until he has seen it break down into its component parts of human beings.
    Mary Heaton Vorse (1874–1966)

    Your Englishman, confronted by something abnormal will always pretend that it isn’t there. If he can’t pretend that, he will look through the object, or round it, or above it or below it, or in any direction except into it. If, however, you force him to look into it, he will at once pretend that he sees the object not for what it is but for something that he would like it to be.
    James Agate (1877–1947)

    When you model yourself on people, you should try to resemble their good sides.
    Molière [Jean Baptiste Poquelin] (1622–1673)