Topic
Distributed Component Object Model
About: Distributed Component Object Model is a research topic. Over the lifetime, 513 publications have been published within this topic receiving 10054 citations. The topic is also known as: DCOM & Network OLE.
Papers published on a yearly basis
Papers
Book•
1 Jan 2001TL;DR: Intended for use in a senior/graduate level distributed systems course or by professionals, this text systematically shows how distributed systems are designed and implemented in real systems.
Abstract: From the Publisher:
Andrew Tanenbaum and Maarten van Steen cover the principles, advanced concepts, and technologies of distributed systems in detail, including: communication, replication, fault tolerance, and security. Intended for use in a senior/graduate level distributed systems course or by professionals, this text systematically shows how distributed systems are designed and implemented in real systems. Written in the superb writing style of other Tanenbaum books, the material also features unique accessibility and a wide variety of real-world examples and case studies, such as NFS v4, CORBA, DOM, Jini, and the World Wide Web.
FEATURES
Detailed coverage of seven key principles.
An introductory chapter followed by a chapter devoted to each key principle: communication, processes, naming, synchronization, consistency and replication, fault tolerance, and security, including unique comprehensive coverage of middleware models.
Four chapters devoted to state-of-the-art real-world examples of middleware. Covers object-based systems, document-based systems, distributed file systems, and coordination-based systems including CORBA, DCOM, Globe, NFS v4, Coda, the World Wide Web, and Jini.
Excellent coverage of timely, advanced, distributed systems topics: Security, payment systems, recent Internet and Web protocols, scalability, and caching and replication.
NEW-The Prentice Hall Companion Website for this book contains PowerPoint slides, figures in various file formats, and other teaching aids, and a link to the author's Web site.
2,457 citations
TL;DR: Object-oriented (OO) application frameworks are a promising technology for reifying proven software designs and implementations in order to reduce the cost and improve the quality of software.
Abstract: Computing power and network bandwidth have increased dramatically over the past decade However, the design and implementation of complex software remains expensive and error-prone Much of the cost and effort stems from the continuous rediscovery and re-invention of core concepts and components across the software industry In particular, the growing heterogeneity of hardware architectures and diversity of operating system and communication platforms makes it hard to build correct, portable, efficient, and inexpensive applications from scratch Object-oriented (OO) application frameworks are a promising technology for reifying proven software designs and implementations in order to reduce the cost and improve the quality of software A framework is a reusable, ``semi-complete'' application that can be specialized to produce custom applications [Johnson:88] In contrast to earlier OO reuse techniques based on class libraries, frameworks are targeted for particular business units (such as data processing or cellular communications) and application domains (such as user interfaces or real-time avionics) Frameworks like MacApp, ET++, Interviews, ACE, Microsoft's MFC and DCOM, JavaSoft's RMI, and implementations of OMG's CORBA play an increasingly important role in contemporary software development
950 citations
TL;DR: The development process at Microsoft helps to determine what works and what doesn't by completely recompiling the source code and executing automated tests.
Abstract: • 20,500 employees • 250 products – Windows 95 • 11 million lines of code • 200 designers, programmers and testers • What development process do they use? Main Philosophy • Does not use adopt too many of the structured software-engineering practices • \" scaled-up \" a loosely structured small-team style (hacker philosophy?) – Small parallel teams of 3 to 8 developers each or – Individual programmers – Working together as a large team Philosophy • Each team has the freedom to evolve their design – Evolve features and whole products incrementally – Occasionally introduce new concepts and technologies • However – Since teams have so much freedom – There is a danger that products may become incompatible – They synchronize their changes frequently Synch-and-stabilize • Terms describing the process – \" daily-build \" – \" nightly build \" – \" zero defect \" – \" milestone \" • Build – Putting together partially completed or finished pieces of the software – Goal • To determine what works and what doesn't – Done by completely recompiling the source code and executing automated tests
224 citations
Book•
1 Jan 1997
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.
211 citations
TL;DR: Middleware has emerged as an important architectural component in modern distributed systems and its role is to offer users a high-level, platform-independent programming model and to hide problems of distribution.
Abstract: Middleware has emerged as an important architectural component in modern distributedsystems. Its role is to offer users a high-level, platform-independent programming model(object-oriented or component-based) and to hide problems of distribution. Examples of keymiddleware platforms include CORBA, DCOM, .NET, and the Java-based series of technologies (RMI, Jini, and EJB).
183 citations
Related Topics (5)
Performance Metrics
| Year | Papers |
|---|---|
| 2025 | 2 |
| 2024 | 6 |
| 2023 | 3 |
| 2022 | 4 |
| 2021 | 1 |
| 2020 | 2 |