1 / 15

DCOM

DCOM. (Overview). by- Jeevan Varma Anga. DCOM Overview. What is DCOM? Why DCOM? Architecture. What is DCOM?. Distributed Component Object Model. “Application-level protocol for object-oriented remote procedure calls.” IETF Internet Draft 5/96. “COM with a longer wire”

ballari-taj
Download Presentation

DCOM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DCOM (Overview) by- Jeevan Varma Anga

  2. DCOM Overview • What is DCOM? • Why DCOM? • Architecture

  3. What is DCOM? Distributed Component Object Model “Application-level protocol for object-oriented remote procedure calls.” IETF Internet Draft 5/96 “COM with a longer wire” Microsoft Press Release 9/96 “Object RPC” The Distributed Component Object Model (DCOM) is a protocol that enables software components to communicate directly over a network in a reliable, secure, and efficient manner. Previously called "Network OLE," DCOM is designed for use across multiple network transports, including Internet protocols such as HTTP.

  4. Why DCOM? • Components And Reuse • Location Independency • Language Neutrality • Connection Management

  5. Location independence

  6. Why DCOM? • Scalability • Symmetric Multiprocessing (SMP) • Flexible Deployment • Robust versioning • Performance • Bandwidth and Latency • Security • Security by configuration • Programatic control • Internet control

  7. Why DCOM? • Load Balancing • Static Load Balancing • Dynamic Load Balancing • Fault Tolerance • Ease of Deployment • Protocol Neutrality • Platform Neutrality

  8. Fault Tolerance

  9. COM/DCOM Architecture Client Server Client Application Server Implementation Proxy Stub Channel • COM Clients • - Proxies map object method • invocations into calls to • COM/DCOM objects • COM Servers • - In-Process • Local • Remote

  10. Overall DCOM Architecture

  11. In-Process Servers

  12. Local Servers

  13. Remote Servers

  14. Summary • DCOM makes it easy to write a distributed application • Provides rich, symmetric communication between components. • Can be robustly expanded to meet new functional requirements. • Takes advantage of existing custom and off-the-shelf components. • Integrates teams proficient in any programming language and development tool. • Uses network bandwidth carefully, while providing great response times for end-users. • Is inherently secure. • Provides a smooth migration path to sophisticated load-balancing and fault-tolerance features. • Can be efficiently deployed and administered. • Can be used with any network protocol and integrated into any hardware platform. • DCOM is the TCP/IP of objects.

  15. Want to know more? • Specification – N. Brown, C. Kindel, “Distributed Component Object Model Protocol -- DCOM/1.0,” IETF Networking Group Internet-Draft, Microsoft Corporation, Jan, 1998 • Programming – R. Grimes, “Professional DCOM Programming”.

More Related