cobra vs dcom
...g a different behavior of the object. COBRA/ CORBA CORBA (Common Object Request Broker Architecture), is a distributed object architecture that allows objects to interoperate across networks regardless of the language in which they were written or the platform on which they are deployed. CORBA allows developers to write applications that are more flexible and future-proof, to wrap legacy systems, and to code in the language they know best. CORBA relies on a protocol called the Internet Inter-ORB Protocol (IIOP) for remoting objects. Everything in the CORBA architecture depends on an Object Request Broker (ORB). The ORB acts as a central Object Bus over which each CORBA object interacts transparently with other CORBA objects located either locally or remotely. Each CORBA server object has an interface and exposes a set of methods. To request a service, a CORBA client acquires an object reference to a CORBA server object. The client can now make method calls on the object reference as if the CORBA server object resided in the client's address space. The ORB is responsible for finding a CORBA object's implementation, preparing it to receive requests, communicate requests to it and carry the reply back to the client. A CORBA object interacts with the ORB either through the ORB interface or through an Object Adapter - either a Basic Object Adapter (BOA) or a Portable Object Adapter (POA). As a result, using the standard protocol IIOP, a CORBA-based program from any vendor, on almost any computer, operating system, programming language, and network, can interoperate with a CORBA-based program from the same or another vendor, on almost any other computer, operating system, programming language, and network. Describe, compare and contrast the two frameworks/models with respect to distributed systems. Similarities 1. DCOM is generally equivalent to the Common Object Request Broker Architecture (COBRA) in terms of providing a set of distributed services. 2. In both DCOM and CORBA, the interactions between a client process and an object server are implemented as object-oriented RPC (remote procedure call) -style communications. To invoke a remote function, the client makes a call to the client stub. The stub packs the call parameters into a request message, and invokes a wire protocol to ship the message to the server. 3. Both DCOM and CORBA frameworks provide client-server type of communications. To request a service, a client invokes a method implemented by a remote object, which acts as the server in the client-server model. The service provided by the server is encapsulated as an object and the interface of an object is described in an Interface Definition Language (IDL) Differences COBRA DCOM i. Supports multiple inheritance at the interface le...