1 / 14

DISTRIBUTED COMPONENT OBJECT MODEL -

DISTRIBUTED COMPONENT OBJECT MODEL -. A STUDY OF ITS ARCHITECTURE AND WHY IT IS CONSIDERED A FAILURE BY EXPERTS. DISTRIBUTED COMPUTING PROTOCOLS. CORBA Java’s RMI DCOM. ADVANTAGES OF DISTRIBUTED COMPUTING. Speeding up development processes Improving deployment flexibility

osric
Télécharger la présentation

DISTRIBUTED COMPONENT OBJECT MODEL -

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. DISTRIBUTED COMPONENT OBJECT MODEL - A STUDY OF ITS ARCHITECTURE AND WHY IT IS CONSIDERED A FAILURE BY EXPERTS.

  2. DISTRIBUTED COMPUTINGPROTOCOLS • CORBA • Java’s RMI • DCOM

  3. ADVANTAGES OF DISTRIBUTED COMPUTING • Speeding up development processes • Improving deployment flexibility • Lowering maintenance costs • Improving scalability • Load balancing

  4. REGISTRIES AND KEYS • A Registry is the place where the components installed in a machine store their settings. • The ‘registry’ contains many sections called keys. The keys contain value data such as Class ID and Application ID.

  5. ARCHITECTURE OF DCOM

  6. THE FIVE COMPONENTS OF DCOM • Object Instantiation Process • Data transferring between clients and components • Security in DCOM • The DCE RPC component • The low-level protocol stack

  7. OBJECT INSTANTIATION PROCESS • Clients use COM’s "create instance" functions such as CoCreateInstanceEx, CoGetClassObject, etc. to create a new instance of a component. • To specify the server on which a component resides, DCOM employs the notion of RemoteServerName

  8. Data transferring between clients and components • Marshaling : is the process of reading parameters from the stack into a flat memory buffer (that will be transferred across "the wire" later.) • Unmarshaling :it reads the memory buffer and re-creates the stack that is the same as the caller’s stack.

  9. Security in DCOM • Access Security • Launch Security • Identity Security • Connection Policy

  10. IS DCOM AN UNQUALIFIED SUCCESS? • Initially, DCOM was a major competitor to CORBA. • There were difficulties in getting them to work over internet firewalls. • DCOM and CORBA lost out to web browsers combined with http requests.

  11. THE MS-BLASTER WORM • DCOM RPC Interface Buffer OverrunVulnerability • TCP port 135is overrun by a large amount of data • This allows the remote system to gain local system privileges on tcp port 4444. • In essence it causes a ‘DENIAL OF SERVICE’ error for microsoftupdate.com. • Microsoft did come up with a patch to rectify the ‘buffer overrun in msrpc’. The patch is available at http://www.microsoft.com/technet/security/bulletin/MS03-026.mspx.

  12. DCOM SUPPORTERS All said and done DCOM is not without its supporters. • SAP • DUNN and BRADSTREET • SYBASE

More Related