From 84adefa331c4159d432d22840663c38f155cd4c1 Mon Sep 17 00:00:00 2001 From: Erlang/OTP Date: Fri, 20 Nov 2009 14:54:40 +0000 Subject: The R13B03 release. --- lib/orber/doc/src/ch_orber_kernel.xml | 102 ++++++++++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 lib/orber/doc/src/ch_orber_kernel.xml (limited to 'lib/orber/doc/src/ch_orber_kernel.xml') diff --git a/lib/orber/doc/src/ch_orber_kernel.xml b/lib/orber/doc/src/ch_orber_kernel.xml new file mode 100644 index 0000000000..6669641432 --- /dev/null +++ b/lib/orber/doc/src/ch_orber_kernel.xml @@ -0,0 +1,102 @@ + + + + +
+ + 19992009 + Ericsson AB. All Rights Reserved. + + + The contents of this file are subject to the Erlang Public License, + Version 1.1, (the "License"); you may not use this file except in + compliance with the License. You should have received a copy of the + Erlang Public License along with this software. If not, it can be + retrieved online at http://www.erlang.org/. + + Software distributed under the License is distributed on an "AS IS" + basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See + the License for the specific language governing rights and limitations + under the License. + + + + The Orber Application + + + 1998-10-05 + + ch_orber_kernel.xml +
+ +
+ ORB Kernel and IIOP +

This chapter gives a brief overview of the ORB and its relation + to objects in a distributed environment and the usage of Domains + in Orber. + Also Internet-Inter ORB Protocol (Internet-Inter ORB Protocol) is discussed and how this + protocol facilitates communication between ORBs to + allow the accessory of persistent server objects in Erlang.

+
+ +
+ The Object Request Broker (ORB) +

An ORB kernel can be best described as the middle-ware, which + creates relationships between clients and servers, but is + defined by its interfaces. This allows transparency for the + user, as they do not have to be aware of where the requested + object is located. Thus, the programmer can work with any other + platform provided that an IDL mapping and interfaces exist. +

+

The IDL mapping which is described in a later chapter is the + translator between other platforms, and languages. However, it + is the ORB, which provides objects with a structure by which + they can communicate with other objects. +

+

ORBs intercept and direct messages from one object, pass this + message using IIOP to another ORB, which then directs the + message to the indicated object. +

+

An ORB is the base on which interfaces, communication stubs + and mapping can be built to enable communication between + objects. Orber uses A domain allows a more efficient communication protocol to be used between objects not on the same node without the need of an ORBto group objects of different nodes +

+

How the ORB provides communication is shown very simply in figure 1 below:

+ + + +Figure 1: How the Object Request Broker works. + +

The domain in Orber gives an extra aspect to the distributed object + environment as each domain has one ORB, but it is distributed over + a number of object in different nodes. The domain binds objects on + nodes more closely than distributed objects in different domains. The + advantage of a domain is that a faster communication exists between + nodes and objects of the same domain. An internal communication protocol + (other than IIOP) allows a + more efficient communication between these objects.

+ +

Unlike objects, domains can only have one name + so that no communication ambiguities exist between domains.

+ +
+ +
+ Internet Inter-Object Protocol (IIOP) +

IIOP is a communication protocol developed by the OMG to + facilitate communication in a distributed object-oriented + environment. +

+

Figure 2 below demonstrates how IIOP works between objects:

+ + + +Figure 2: IIOP communication between domains and objects. + + +

Within the Orber domains the objects communicate without + using the IIOP. However, the user is unaware of the difference in protocols, as this difference is not visible.

+ +
+ + -- cgit v1.2.3