About: Component Object Model is a research topic. Over the lifetime, 386 publications have been published within this topic receiving 5572 citations. The topic is also known as: COM.
TL;DR: In this paper, a method and apparatus for mapping address information (e.g., locations denoted by name or address, street addresses, landmarks, etc.) off of disparate sources and onto new or existing maps, are disclosed.
Abstract: A method and apparatus for mapping address information (e.g. locations denoted by name or address, street addresses, landmarks, etc.) off of disparate sources and onto new or existing maps, are disclosed. A mapping component (e.g. a standalone application, a web-browser plug-in, an ActiveX control, a DLL, a COM object, a web object, a part of a an application displaying and/or generating maps, etc.) running on an electronic device (e.g. personal computer, workstation, thin client, PDA, cellular phone, GPS device, etc.) may receive input of address information and relay the received input to a mapping application (e.g. an online mapping service such as Google Maps®, Yahoo! Maps®, Windows Live Search Maps®, MapQuest®, etc.; or a mapping application running locally on a PDA, cell phone, etc.) for plotting on a common map, displayed by a map-display application (e.g. a browser, a web user agent, etc.). A mapping component may have a permanent visibility to the user (e.g. by being a top-most application in a windowed environment, by being present in a portion of the user's desktop that is commonly unobstructed by other applications such as the system tray, by being a widget, by being a control on a browser toolbar, etc.) A mapping component may be a module of a display application. A mapping component may receive user input directly, for example by typing; and/or via the clipboard, for example via a drag-and-drop or copy/paste operation or a pre-determined key combination; and/or via the use of context menus; and/or by any other means supported by the electronic device. A mapping component may aggregate multiple received address information prior to relaying the aggregated address information to a mapping application and/or a map-display application. A mapping component may parse, or otherwise process the location data prior to relaying the location data to a mapping application and/or a map-display application. The user may select an existing map for receiving the input; or, the optimal map for displaying the address information may be selected automatically; or, a mapping service may associate the user with stored maps and select the optimal map for receiving the address information.
TL;DR: In this article, the authors discuss how to use COM and DCOM with existing legacy systems, how they fit into two-and three-tier client/server architectures, "Thin" versus "Thick Clients" and how they relate to Microsoft's Active Server Platform.
Abstract: Component Object Model (COM) and Distributed Component Object Model (DCOM) provide the foundation for Microsoft's distributed object strategy. They are the glue that should enable Microsoft to bring their other core products and technologies such as ActiveX, Internet Information Server, and Internet Explorer to the enterprise. In other words, this is Microsoft's answer to CORBA, Netscape, and JavaBeans. This text discusses: how to use COM and DCOM with existing legacy systems; how COM and DCOM fit into two- and three-tier client/server architectures; "Thin" versus "Thick Clients" and how they relate to Microsoft's Active Server Platform; new technologies from Microsoft such as Viper and Falcon; and security issues for distributed objects.
TL;DR: In this paper, a control system methodology using object-oriented software to integrate multiple control systems into a common object model is presented. Butler et al. present a system that provides both a browser client (running on a Java-enabled browser) and a server client (121).
Abstract: A control system methodology uses object-oriented software to integrate multiple control systems into a common object model. Object-oriented techniques are used to construct distributed Java-based applications in a multi-vendor open system environment for use in controlling and monitoring systems of varying size and configuration. The system provides both a browser client (101) (running on a Java-enabled browser) and a server client (121). The present invention has multiple stations: a Web BAS Server (110), a Network Processor (NP) (111), and a Field Controller (FC) (112). The NP and FC are preferably Java Virtual Machines implemented in a plug-in Java Modular Environment. Information is brought into a common object model and made available throughout the system. A custom programming language based on Java is provided for object creation, with access to objects controlled through a multi-level security protocol. Data flow is governed by a real-time information synchronization manager.
TL;DR: The programming interface and implementation of the repository engine and the Open Information Model are described, which implements a set of object-oriented interfaces on top of a SQL database system.
TL;DR: Middleware is everywhere, and this new column explores the challenges of integrating increasingly diverse and complex computing systems.
Abstract: Middleware is all about integration. Middleware has existed in various forms for many years in systems such as the IBM Customer Information Control System (CICS), numerous message queuing systems such as IBM's MQ Series, the Common Object Request Broker Architecture (CORBA), Microsoft's Component Object Model (COM), Java 2 Enterprise Edition (J2EE), and the latest rage, Web services. Virtually every form of application, programming language, operating system, and hardware has been a target of an integration effort involving these middleware systems or their cousins. Middleware is everywhere.