CORBA is a standard that allows applications written in different programming languages and running on different operating systems to communicate. It uses Interface Definition Language (IDL) to specify interfaces that objects present and defines how to map IDL to programming languages. CORBA enables seamless interoperability between distributed, heterogeneous applications.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
86 views10 pages
Corba
CORBA is a standard that allows applications written in different programming languages and running on different operating systems to communicate. It uses Interface Definition Language (IDL) to specify interfaces that objects present and defines how to map IDL to programming languages. CORBA enables seamless interoperability between distributed, heterogeneous applications.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 10
What is CORBA?
CORBA is the acronym for Common
Object Request Broker Architecture It was developed by the Object Management Group (OMG) It is an open vendor-independent architecture and infrastructure that computer applications use to work together over networks. Using a standard protocol IIOP (Internet Inter- Orb Protocol), 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. CORBA enables software written in different languages and running on different computers to work with each other seamlessly. Implementation details from specific operating systems, programming languages, and hardware platforms are all removed from the responsibility of developers who use CORBA.
What is CORBA good for?
CORBA is useful in many situations. Because of the easy way that CORBA integrates machines from so many vendors, with sizes ranging from mainframes and desktops to hand-helds and embedded systems, it is the middleware of choice for large (and even not-so-large) enterprises. It is used in servers that must handle large number of clients, at high hit rates, with high reliability. It is scalable and fault tolerant. CORBA works behind the scenes in the computer rooms of many of the world's largest websites; ones that you probably use every day. IDL CORBA uses an interface definition language (IDL) to specify the interfaces which objects present to the outer world. CORBA then specifies a mapping from IDL to a specific implementation language like C++or Java. Standard mappings exist for Ada, C, C++, C++11, Lisp, Ruby, Smalltalk, Java, C OBOL, PL/I and Python. There are also non-standard mappings for Perl, Visual Basic, Erlang, and Tcl implemented by object request brokers
The CORBA specification dictates there shall be an ORB through which an application would interact with other objects.(ORBs) written for those languages. 1. The application simply initializes the ORB, and accesses an internal Object Adapter, which maintains things like reference counting, object (and reference) instantiation policies, and object lifetime policies.
2. The Object Adapter is used to register instances of the generated code classes. Generated code classes are the result of compiling the user IDL code, which translates the high-level interface definition into an OS- and language- specific class base for use by the user application. This step is necessary in order to enforce CORBA semantics and provide a clean user process for interfacing with the CORBA infrastructure. Some IDL mappings are more difficult to use than others. For example, due to the nature of Java, the IDL-Java mapping is rather straightforward and makes usage of CORBA very simple in a Java application.
The diagram below illustrates how the generated code is used within the CORBA infrastructure