Common Object Request Broker Architecture: Difference between revisions

Revision as of 14:18, 24 May 2003

Revision as of 14:20, 24 May 2003

Line 6:

In a general sense CORBA "wraps" code written in another language into a bundle containing additional information on the capabilities of the code inside, and how to call it. The resulting wrapped objects can then be called from other programs (or CORBA objects) over the network. In this sense CORBA can be considered as a machine-readable documentation format, similar to a [[header file]] but with considerably more information.

CORBA uses an [[Interface Definition Language]], or [[IDL]], to specify the interfaces that objects will present to the world. CORBA then specifies a "mapping" from IDL to a specific implementation language like [[c_plus_plusC plus plus|C++]] or [[Java_programming_languageJava programming language|Java]]. This mapping precisely describes how the CORBA data types are to be used in both client and server implementations. Standard mappings exist for [[C_languageC language|C]], C++, [[Smalltalk|Smalltalk]], Java and [[Python_programming_languagePython programming language|Python]]. There are also non-standard mappings for [[Perl]] and [[Tcl]] implemented by ORBs written for those languages.

(CORBA IDL is only one example of an IDL)

Line 14:

CORBA is more than just a language and platform neutral [[remote procedure call]] specification. It defines commonly needed services such as transactions and security.

==External link==

=== Additional Resources ===

* http://www.omg.org/