<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<title>Some basic explanations</title>
<link rel="stylesheet" href="../../../doc/src/boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
<link rel="home" href="../index.html" title="The Boost C++ Libraries BoostBook Documentation Subset">
-<link rel="up" href="../interprocess.html" title="Chapter 12. Boost.Interprocess">
+<link rel="up" href="../interprocess.html" title="Chapter 14. Boost.Interprocess">
<link rel="prev" href="quick_guide.html" title="Quick Guide for the Impatient">
<link rel="next" href="sharedmemorybetweenprocesses.html" title="Sharing memory between processes">
</head>
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="interprocess.some_basic_explanations"></a><a class="link" href="some_basic_explanations.html" title="Some basic explanations">Some basic explanations</a>
</h2></div></div></div>
-<div class="toc"><dl>
+<div class="toc"><dl class="toc">
<dt><span class="section"><a href="some_basic_explanations.html#interprocess.some_basic_explanations.processes_and_threads">Processes
And Threads</a></span></dt>
<dt><span class="section"><a href="some_basic_explanations.html#interprocess.some_basic_explanations.sharing_information">Sharing
running and each process has its own address space. To share information
between processes we have several alternatives:
</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem">
Two processes share information using a <span class="bold"><strong>file</strong></span>.
To access to the data, each process uses the usual file read/write mechanisms.
In <span class="bold"><strong>Boost.Interprocess</strong></span>, we can have 3 types
of persistence:
</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem">
<span class="bold"><strong>Process-persistence</strong></span>: The mechanism lasts
until all the processes that have opened the mechanism close it, exit
persistence:
</p>
<div class="table">
-<a name="interprocess.some_basic_explanations.persistence.t0"></a><p class="title"><b>Table 12.1. Boost.Interprocess Persistence Table</b></p>
+<a name="interprocess.some_basic_explanations.persistence.t0"></a><p class="title"><b>Table 14.1. Boost.Interprocess Persistence Table</b></p>
<div class="table-contents"><table class="table" summary="Boost.Interprocess Persistence Table">
<colgroup>
<col>
between UNIX systems. For this reason, <span class="bold"><strong>Boost.Interprocess</strong></span>
limits this name to a C++ variable identifier or keyword:
</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem">
Starts with a letter, lowercase or uppercase, such as a letter from a
to z or from A to Z. Examples: <span class="emphasis"><em>Sharedmemory, sharedmemory,
memory, memory mapped files, named mutexes/conditions/semaphores) have kernel
or filesystem persistency. This means that even if all processes that have
opened those resources end, the resource will still be accessible to be opened
- again and the resource can only be destructed via an explicit to their static
- member <code class="computeroutput"><span class="identifier">remove</span></code> function. This
- behavior can be easily understood, since it's the same mechanism used by
- functions controlling file opening/creation/erasure:
+ again and the resource can only be destructed via an explicit call to their
+ static member <code class="computeroutput"><span class="identifier">remove</span></code> function.
+ This behavior can be easily understood, since it's the same mechanism used
+ by functions controlling file opening/creation/erasure:
</p>
<div class="table">
-<a name="interprocess.some_basic_explanations.constructors_destructors_and_resource_lifetime.t0"></a><p class="title"><b>Table 12.2. Boost.Interprocess-Filesystem Analogy</b></p>
+<a name="interprocess.some_basic_explanations.constructors_destructors_and_resource_lifetime.t0"></a><p class="title"><b>Table 14.2. Boost.Interprocess-Filesystem Analogy</b></p>
<div class="table-contents"><table class="table" summary="Boost.Interprocess-Filesystem Analogy">
<colgroup>
<col>
memory and named semaphores:
</p>
<div class="table">
-<a name="interprocess.some_basic_explanations.constructors_destructors_and_resource_lifetime.t1"></a><p class="title"><b>Table 12.3. Boost.Interprocess-POSIX shared memory</b></p>
+<a name="interprocess.some_basic_explanations.constructors_destructors_and_resource_lifetime.t1"></a><p class="title"><b>Table 14.3. Boost.Interprocess-POSIX shared memory</b></p>
<div class="table-contents"><table class="table" summary="Boost.Interprocess-POSIX shared memory">
<colgroup>
<col>
</table></div>
</div>
<br class="table-break"><div class="table">
-<a name="interprocess.some_basic_explanations.constructors_destructors_and_resource_lifetime.t2"></a><p class="title"><b>Table 12.4. Boost.Interprocess-POSIX named semaphore</b></p>
+<a name="interprocess.some_basic_explanations.constructors_destructors_and_resource_lifetime.t2"></a><p class="title"><b>Table 14.4. Boost.Interprocess-POSIX named semaphore</b></p>
<div class="table-contents"><table class="table" summary="Boost.Interprocess-POSIX named semaphore">
<colgroup>
<col>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"></td>
-<td align="right"><div class="copyright-footer">Copyright © 2005-2011 Ion Gaztanaga<p>
+<td align="right"><div class="copyright-footer">Copyright © 2005-2012 Ion Gaztanaga<p>
Distributed under the Boost Software License, Version 1.0. (See accompanying
file LICENSE_1_0.txt or copy at <a href="http://www.boost.org/LICENSE_1_0.txt" target="_top">http://www.boost.org/LICENSE_1_0.txt</a>)
</p>