Common Object Request Broker Architecture: Difference between revisions

Revision as of 11:19, 25 September 2002

Revision as of 11:24, 25 September 2002

Line 3:

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.

These sorts ofCORBA systemsuses are generally referred to asan [[Interface Definition Language]]s, or ''IDL's'', ofto specify the interfaces that objects will present to the world. which CORBA IDL is only one example of an ''IDL''. In theory the use of an IDL should provide language independance for the code used to implement the object, but in practice the IDL often takes on characteristics of one target language. Such is the case for CORBA, which is used almost exclusively with [[C plus plus|C++]].

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