/usr/share/doc/polyorb-doc/html/polyorb_ug/Architecture-of-a-Distributed-Ada-Application.html

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- This is free software; you can redistribute it and/or modify it under
terms of the GNU General Public License as published by the Free
Software Foundation; either version 3, or (at your option) any later
version.  This software is distributed in the hope that it will be
useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.

You should have received a copy of the GNU General Public License and
a copy of the GCC Runtime Library Exception along with this program;
see the files COPYING3 and COPYING.RUNTIME respectively.  If not, see
<http://www.gnu.org/licenses/>. -->
<!-- Created by GNU Texinfo 5.2, http://www.gnu.org/software/texinfo/ -->
<head>
<title>PolyORB User&rsquo;s Guide: Architecture of a Distributed Ada Application</title>

<meta name="description" content="PolyORB User&rsquo;s Guide: Architecture of a Distributed Ada Application">
<meta name="keywords" content="PolyORB User&rsquo;s Guide: Architecture of a Distributed Ada Application">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="About-This-Guide.html#About-This-Guide" rel="start" title="About This Guide">
<link href="Index.html#Index" rel="index" title="Index">
<link href="About-This-Guide.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Introduction-to-the-Ada-DSA.html#Introduction-to-the-Ada-DSA" rel="up" title="Introduction to the Ada DSA">
<link href="Categorization-Pragmas.html#Categorization-Pragmas" rel="next" title="Categorization Pragmas">
<link href="Introduction-to-the-Ada-DSA.html#Introduction-to-the-Ada-DSA" rel="prev" title="Introduction to the Ada DSA">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.indentedblock {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
div.smalllisp {margin-left: 3.2em}
kbd {font-style:oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space:nowrap}
span.nolinebreak {white-space:nowrap}
span.roman {font-family:serif; font-weight:normal}
span.sansserif {font-family:sans-serif; font-weight:normal}
ul.no-bullet {list-style: none}
-->
</style>


</head>

<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="Architecture-of-a-Distributed-Ada-Application"></a>
<div class="header">
<p>
Next: <a href="Categorization-Pragmas.html#Categorization-Pragmas" accesskey="n" rel="next">Categorization Pragmas</a>, Previous: <a href="Introduction-to-the-Ada-DSA.html#Introduction-to-the-Ada-DSA" accesskey="p" rel="prev">Introduction to the Ada DSA</a>, Up: <a href="Introduction-to-the-Ada-DSA.html#Introduction-to-the-Ada-DSA" accesskey="u" rel="up">Introduction to the Ada DSA</a> &nbsp; [<a href="About-This-Guide.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Architecture-of-a-Distributed-Ada-Application-1"></a>
<h4 class="subsection">8.1.1 Architecture of a Distributed Ada Application</h4>

<p>A distributed system is an interconnection of one or more processing
nodes and zero or more storage nodes. A distributed program comprises
one or more partitions. A partition is an aggregate of library
units. Partitions communicate through shared data or RPCs. A passive
partition has no thread of control. Only a passive partition can be
configured on a storage node. An active partition has zero or more
threads of control and has to be configured on a processing node.
</p>
<p>The library unit is the core component of a distributed Ada
application. The user can explicitly assign library units to a
partition. Partitioning is a post-compilation process. The user
identifies interface packages at compile-time. These packages are
categorized using pragmas. Each of these pragmas supports the use of one of
the following classical paradigms:
</p>
<ul>
<li> Remote subprograms:
For the programmer, a remote subprogram call is similar to a regular
subprogram call. Run-time binding using access-to-subprogram types can
also be used with remote subprograms. These remote subprograms are
declared in library units categorized as remote call interface
(RCI).

</li><li> Distributed objects:
Special-purpose access types can designate remote
objects. When a primitive dispatching operation is invoked on an object
designated by such a remote access, a remote call is performed transparently
on the partition on which the object resides. The types of these distributed
objects are declared in library units categorized as remote types (RT).

</li><li> Shared objects:
Global data can be shared among active partitions, providing a
repository similar to shared memory, a shared file system or a
database. Entryless protected objects allow safe concurrent access and update
of shared objects. This feature is orthogonal to the notion of distributed
objects, which are only accessed through exported services. These shared
objects are declared in library units categorized as shared passive (SP).

</li></ul>

<p>The remotely-called subprograms declared in a library unit categorized
as remote call interface (RCI) or remote types (RT) may be either
statically or dynamically bound. The partition on which a statically
bound remote subprogram is executed can be determined before the
call. This is a static remote subprogram call. In contrast, a remote method or
a dereference of an access to remote subprogram are dynamically bound remote
calls, because the partition on which the remote subprogram is executed
is determined at runtime, by the actuals of the call.
</p>
<p>In the following example, Data_1 and Data_2 are shared passive (SP)
library units. Data_1 is configured on a passive partition mapped on a
storage node. Partition_1 and Partition_2 are active partitions. Note
that under some circumstances, a partition, for instance Partition_2,
can be duplicated. To be duplicated, Unit_2 and Unit_3 which are
configured on Partition_2 have to provide only dynamically bound remote
subprograms. Otherwise, a partition calling a remote subprogram on
Unit_2 would not be able to statically determine where to perform the
remote call between the two instances of Unit_2.
</p>
<br>
<br>
<img src="xe-arch.fig.png" alt="xe-arch.fig">
<br>

<hr>
<div class="header">
<p>
Next: <a href="Categorization-Pragmas.html#Categorization-Pragmas" accesskey="n" rel="next">Categorization Pragmas</a>, Previous: <a href="Introduction-to-the-Ada-DSA.html#Introduction-to-the-Ada-DSA" accesskey="p" rel="prev">Introduction to the Ada DSA</a>, Up: <a href="Introduction-to-the-Ada-DSA.html#Introduction-to-the-Ada-DSA" accesskey="u" rel="up">Introduction to the Ada DSA</a> &nbsp; [<a href="About-This-Guide.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
</div>



</body>
</html>
polyorb-doc 2.11~20140418-3 / usr / share / doc / polyorb-doc / html / polyorb_ug / Architecture-of-a-Distributed-Ada-Application.html
