svn commit: r1027548 - in /websites/staging/directory/trunk/content: ./ api/internal-design-guide/5-network.html

[bu...@apache.org]

Author: buildbot
Date: Thu Mar 29 08:49:43 2018
New Revision: 1027548

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/api/internal-design-guide/5-network.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Mar 29 08:49:43 2018
@@ -1 +1 @@
-1827964
+1827965

Modified: websites/staging/directory/trunk/content/api/internal-design-guide/5-network.html
==============================================================================
--- websites/staging/directory/trunk/content/api/internal-design-guide/5-network.html (original)
+++ websites/staging/directory/trunk/content/api/internal-design-guide/5-network.html Thu Mar 29 08:49:43 2018
@@ -187,68 +187,16 @@ h2:hover > .headerlink, h3:hover > .head
 <h1 id="5-network">5 - Network<a class="headerlink" href="#5-network" title="Permanent link">&para;</a></h1>
 <h1 id="content">Content<a class="headerlink" href="#content" title="Permanent link">&para;</a></h1>
 <ul>
-<li><a href="class-hierarchy">Class hierarchy</a></li>
-<li><a href="mina-usage">MINA usage</a></li>
-<li>
-<ul>
-<li><a href="initialization">Initialization</a></li>
-</ul>
-</li>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="example-using-a-ldapconnectionconfig">Example : using a LdapConnectionConfig</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li>
-<ul>
-<li><a href="mina-events-processing">MINA Events processing</a></li>
-</ul>
-</li>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="events-processing">Events processing</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="sending-a-message">Sending a message</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="receiving-a-message">Receiving a message</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="encoding-decoding">Encoding/decoding</a></li>
-</ul>
-</li>
-</ul>
-</li>
-<li>
-<ul>
-<li><a href="startts-handling">StartTLS handling</a></li>
-</ul>
-</li>
+<li><a href="#class-hierarchy">Class hierarchy</a></li>
+<li><a href="#mina-usage">MINA usage</a>
+<strong> <a href="#initialization">Initialization</a>
+<strong><em> <a href="#example-using-a-ldapconnectionconfig">Example : using a LdapConnectionConfig</a>
+</em>* <a href="#mina-events-processing">MINA Events processing</a>
+</strong>* <a href="#events-processing">Events processing</a>
+<strong><em> <a href="#sending-a-message">Sending a message</a>
+</em></strong> <a href="#receiving-a-message">Receiving a message</a>
+</strong><em> <a href="#encoding-decoding">Encoding/decoding</a>
+</em>* <a href="#startts-handling">StartTLS handling</a></li>
 </ul>
 <p>The <strong>Apache LDAP AP</strong> is built on top of <a href="http://mina.apache.org">**Apache MINA</a> which is a <strong>NIO</strong> framework. </p>
 <p>As <strong>MINA</strong> is fully asynchronous, it has some impact on the design of the <strong>LDAP API</strong>. Basically, we send requests, and we don't wait for responses, we get informed when the response is there. Most of the time, the <strong>API</strong> users will want to wait for a response, instead of leveraging the asyncrhonous aspect of the <strong>API</strong>: this is the reason we have a blocking <strong>API</strong>, based on the non-blocking implementation. We will explain the whole thing here.</p>