Component Object Model

(redirected from COM server)

Component Object Model

(programming)
(COM) An open software architecture from DEC and Microsoft, allowing interoperation between ObjectBroker and OLE. Microsoft evolved COM into DCOM.

On page XV of Box's book in the foreword by Charlie Kindel he says, "It is Mark Ryland's fault that some people call COM the 'Common Object Model.' He deeply regrets it and apologizes profusely."

["Essential COM", Don Box].

References in periodicals archive ?
com server, which took it over from the Twitter account @vtellier.The photo really comes from Calais and dates back to July 2015.
Extension of the dynamic Fahrgastinformationssytems (FIS) to a new computer stops with connections from LAN components COM server, WEB-IO, extension of the FIS server functions, the panorama board computer (PTR) and the communication server (KAS).
An OPC UA wrapper is best described as a core providing an OPC UA interface which contains an OPC COM server.
Conversely, it also can function as a COM server and allow external applications, such as MS Excel, MS Word or National Instruments LabVIEW to control it.
The beauty of this is that the COM client program using Origin as the COM server can be very simple, requiring only a few lines of code to implement (well, if you don't count all of the code going into the language itself and all of its associated libraries).
The remaining statements are basically to pass commands and data to the Origin COM server. Some of these statements are direct commands supported in the COM interface, while others are 'simply' passing back LabTalk commands for Origin to execute.
Perhaps the most important point to understand about the VB .NET language is that it is only capable of producing code that can execute within the .NET run-time (you could never use VB .NET to build a classic COM server).
VB is popular due to its ability to build complex user inter- faces, code libraries (e.g., COM servers), and data access logic with minimal fuss and bother.
The COM servers that are created to run under the COM+ runtime have a very different look and feel from the ASP pages that invoke them.
This typically includes installing all necessary executables and DLLs, creating required registry entries, checking if prerequisites are installed or install them, registering services, COM servers or fonts and many other options.
Additionally, the different types of COM servers and the steps involved in creating COM servers are discussed.