ScholarLens Back to search
2002•Apress eBooksRequires access

The Anatomy of a COM Server

Andrew Troelsen

Open publisher page 3 citations

Abstract

In terms of software longevity, Microsoft’s Component Object Model (COM) has enjoyed a lengthy and successful life. Formally solidified circa 1993, COM formalized a specific process for building reusable, binary software components. When developers abide by the rules of COM, they are presented with a number of desirable byproducts. One of the great byproducts of COM components is their language-independent nature. This trait allows software developers to build COM servers in one language (such as VB 6.0) and reuse them in any number of other COM-aware languages (such as C++). However, depending on your programming tool of choice, the internal composition of a COM server may be a bit of a mystery. These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

About this research paper

What this paper is about

In terms of software longevity, Microsoft’s Component Object Model (COM) has enjoyed a lengthy and successful life. Formally solidified circa 1993, COM formalized a specific process for building reusable, binary software components. When developers abide by the rules of COM, they are presented with a number of desirable byproducts. One of the great byproducts of COM components is their language-independent nature. This trait allows software developers to build COM servers in one language (such as VB 6.0) and reuse them in any number of other COM-aware languages (such as C++). However, depending on your programming tool of choice, the internal composition of a COM server may be a bit of a mystery. These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Why it matters

OpenAlex reports 3 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

In terms of software longevity, Microsoft’s Component Object Model (COM) has enjoyed a lengthy and successful life. Formally solidified circa 1993, COM formalized a specific process for building reusable, binary software components. When developers abide by the rules of COM, they are presented with a number of desirable byproducts. One of the great byproducts of COM components is their language-independent nature. This trait allows software developers to build COM servers in one language (such as VB 6.0) and reuse them in any number of other COM-aware languages (such as C++). However, depending on your programming tool of choice, the internal composition of a COM server may be a bit of a mystery. These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Key concepts: Computer science, Component Object Model, Component (thermodynamics), Reuse, Software, Component-based software engineering, Software engineering, Object (grammar)

Related papers

Related paper 1Related paper 2Related paper 3
Back to paper searchBrowse research topicsOriginal source
The Anatomy of a COM Server — Research Paper | ScholarLens