What is an ORB?
Article ID: KB0092096
Updated On:
| Products | Versions |
|---|---|
| Not Applicable | - |
Description
Resolution:
An ORB is, essentially, an object-oriented program written in languages like C , Java or smalltalk, which allows you to make/invoke method, calls on objects within the program.
Some object classes are generated from an IDL definition by the ORB compiler. <br>The ORB provides hidden functionality such that when you invoke method calls on these "ORB generated" objects you do not need to know the exact location of these objects (i.e. which server they reside on).
The method invocation on the object may have to go over the wire to a real object located on another network, carry out the real invocation on this remote node, then bring back the results to the point of the original invocation and pass them back to the invoking application.
The fact that the invocation had to go over the wire to satisfy the method invocation may not be apparent to the invoker.
In this case the object actually held on the client side is merely a proxy to the real object located elsewhere.
The user does not need to be aware of that fact.
This approach is possible in any object-oriented language as mentioned above, provided that there is ORB compiler support for that language (i.e. the ORB compiler could take the object description from the IDL file and generate its "special" version of the class in the given language.
TIB/ObjectBus has ORB compilers for the C language and the Java language. However, for these "special" classes to work and go over the wire when necessary, they also need to use some communication machinery. The ORB libraries and any other routing machinery such as TIB/Rendezvous provide this.
An ORB is, essentially, an object-oriented program written in languages like C , Java or smalltalk, which allows you to make/invoke method, calls on objects within the program.
Some object classes are generated from an IDL definition by the ORB compiler. <br>The ORB provides hidden functionality such that when you invoke method calls on these "ORB generated" objects you do not need to know the exact location of these objects (i.e. which server they reside on).
The method invocation on the object may have to go over the wire to a real object located on another network, carry out the real invocation on this remote node, then bring back the results to the point of the original invocation and pass them back to the invoking application.
The fact that the invocation had to go over the wire to satisfy the method invocation may not be apparent to the invoker.
In this case the object actually held on the client side is merely a proxy to the real object located elsewhere.
The user does not need to be aware of that fact.
This approach is possible in any object-oriented language as mentioned above, provided that there is ORB compiler support for that language (i.e. the ORB compiler could take the object description from the IDL file and generate its "special" version of the class in the given language.
TIB/ObjectBus has ORB compilers for the C language and the Java language. However, for these "special" classes to work and go over the wire when necessary, they also need to use some communication machinery. The ORB libraries and any other routing machinery such as TIB/Rendezvous provide this.
Issue/Introduction
What is an ORB?
Environment
Product: TIBCO ObjectBus
Version: 3.0.0
OS: All
--------------------
Feedback
Yes
No
Powered by
