This file is indexed.

/usr/share/doc/polyorb-doc/html/polyorb_ug/Overview-of-Pragma-Remote_005fCall_005fInterface.html is in polyorb-doc 2.11~20140418-3.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
<!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: Overview of Pragma Remote_Call_Interface</title>

<meta name="description" content="PolyORB User&rsquo;s Guide: Overview of Pragma Remote_Call_Interface">
<meta name="keywords" content="PolyORB User&rsquo;s Guide: Overview of Pragma Remote_Call_Interface">
<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="Pragma-Remote_005fCall_005fInterface.html#Pragma-Remote_005fCall_005fInterface" rel="up" title="Pragma Remote_Call_Interface">
<link href="Regular-Remote-Subprograms-_0028RCI_0029.html#Regular-Remote-Subprograms-_0028RCI_0029" rel="next" title="Regular Remote Subprograms (RCI)">
<link href="Pragma-Remote_005fCall_005fInterface.html#Pragma-Remote_005fCall_005fInterface" rel="prev" title="Pragma Remote_Call_Interface">
<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="Overview-of-Pragma-Remote_005fCall_005fInterface"></a>
<div class="header">
<p>
Next: <a href="Regular-Remote-Subprograms-_0028RCI_0029.html#Regular-Remote-Subprograms-_0028RCI_0029" accesskey="n" rel="next">Regular Remote Subprograms (RCI)</a>, Previous: <a href="Pragma-Remote_005fCall_005fInterface.html#Pragma-Remote_005fCall_005fInterface" accesskey="p" rel="prev">Pragma Remote_Call_Interface</a>, Up: <a href="Pragma-Remote_005fCall_005fInterface.html#Pragma-Remote_005fCall_005fInterface" accesskey="u" rel="up">Pragma Remote_Call_Interface</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="Overview-of-Pragma-Remote_005fCall_005fInterface-1"></a>
<h4 class="subsubsection">8.1.4.1 Overview of Pragma Remote_Call_Interface</h4>

<p>Library units categorized with this pragma declare subprograms that can be
called and executed remotely. An RCI unit acts as a server for remote calls.
There is no memory space shared between server and clients.
A subprogram call that invokes one such
subprogram is a classical RPC operation; it is a
statically bound operation, because the compiler can determine the identity
of the subprogram being called.
</p>
<p>Dynamically bound calls are provided through two mechanisms:
</p>
<ul>
<li> The dereference of an access-to-subprogram value, i.e. a value whose type is
a remote access-to-subprogram (RAS).

</li><li> A dispatching call whose controlling argument is
an access-to-class-wide operand.
The formal is a remote access-to-class-wide (RACW)
type. These remote access types can be declared in RCI
packages as well.

</li></ul>

<p>A remote access type (RAS or RACW) can be viewed as a fat pointer, that is
to say a structure with a remote address and a local address (like an URL:
<tt>&lt;protocol&gt;</tt>://<tt>&lt;remote<code>-</code>machine&gt;</tt>/<tt>&lt;local<code>-</code>directory&gt;</tt>). The
remote address must denote the host of the partition on which the entity has
been created; the local address describes the local memory
address within the host.
</p>
<p>It is very unlikely that RCI units can be duplicated in the distributed
system. An implementation may allow separate copies of a RCI unit as
long as it ensures that the copies present a consistent state to all clients.
In the general case, preserving consistency is very costly. For this reason, the
implementation may require a RCI unit to be unique in the distributed
system.
</p>



</body>
</html>