| Previous | Table of Contents | Next |
In the case of immediate bridging (i.e., not via a standardized, external protocol) the means of communication between the
client-side bridge component and that on the server-side is an entirely private matter. One possible engineering technique
optimizes this communication by coalescing the two components into the same system or even the same address space. In the
latter case, accommodations must be made by both ORBs to allow them to share the same execution environment.
Similar observations apply to request-level bridges, which in the case of collocated ORBs use a common binary interface to
all OMG IDL-defined data as their mediating data format.
Inter-ORB messaging Intra-ORB messaging
Figure 14-3 When the two ORBs are collocated in a bridge execution environment, network communications will be purely intra-ORB.
If the ORBs are not collocated, such communications must go between ORBs.
An advantage of using bridges spanning collocated ORBs is that all external messaging can be arranged to be intra-ORB, using
whatever message-passing mechanisms each ORB uses to achieve distribution within a single ORB, multiple machine system. That
is, for bridges between networked ORBs such a bridge would add only a single “hop,? a cost analogous to normal routing.