Skip to main content

Chapter 4 · Watch, then practise

Distributed Heterogeneous Applications and CORBA

Use CORBA to understand how an interface contract connects applications written in different languages. Trace a remote object invocation through generated code and object request brokers.

3 questions · 3 with related videos. Matches are based on playlist titles; broader background matches are labeled.

What to study

  • IDL contracts
  • Stubs and skeletons
  • ORB and IIOP

Chapter playlists

Choose a playlist

Notes

Part-127: Purpose of an interface Definition Language(IDL),Reason for CORBA not just using the Java

Knowledge Hub · 5:13

The chapter playlist’s IDL lecture directly addresses language-independent interfaces and CORBA.

1. Interface versus implementation

How can a Java client call an object implemented in C++ through CORBA?

Both use an interface expressed in OMG IDL and the corresponding language mappings. The contract specifies operations and parameter types while hiding implementation details. Generated bindings convert between language values and agreed wire representations.

CORBA Architecture | Part-1/2 | Distributed Systems | Lec-45 | Bhanu Priya

Education 4u · 5:56

Supplementary CORBA architecture lecture for the stub, ORB and server invocation path.

2. Trace an invocation

Put client stub, ORB, server skeleton and object implementation in the path of a typical CORBA call.

The client calls its stub, which passes the invocation through the client ORB. For a remote object, the request reaches the server ORB, then the skeleton and implementation. The result travels back through the corresponding layers.

CORBA Architecture | Part-1/2 | Distributed Systems | Lec-45 | Bhanu Priya

Education 4u · 5:56 · Background lecture

CORBA architecture background; the cart-object reference example is explained in the written answer.

3. Object identity example

A shopping service has two cart objects with the same interface. How does a client select its own cart?

It uses the intended instance’s object reference, not only the interface name. The ORB uses that reference to route the invocation. IIOP supplies an interoperable protocol for communication between ORBs.

References