Common Object Request Broker Architecture: Difference between revisions

Revision as of 04:49, 26 September 2002

Revision as of 05:07, 26 September 2002

Line 4:

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 IDLthen isspecifies onlya one"mapping" examplefrom of an ''IDL''. Into theorya thespecific useimplementation oflike an[[c_plus_plus|C++]] IDLor should[[Java_programming_language|Java]]. provideThis languagemapping independanceprecisely fordescribes how the codeCORBA useddata totypes implementare theto object,be butused in practiceboth theclient IDLand oftenserver takesimplementations. onStandard characteristicsmappings ofexist onefor targetC++, languageJava and [[Python_programming_language|Python]]. SuchThere isare thealso casenon-standard mappings for CORBA,[[Perl]] whichand is[[Tcl]] usedimplemented almostby exclusivelyORBs withwritten [[Cfor plusthose plus|C++]]languages.

(CORBA IDL is only one example of an ''IDL'')

CORBA is most widely used with C++ or Java, but it is also usable with Python and Perl, and therefore allows easy interoperability between all those languages.

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