svn commit: r1003802 - in /websites/staging/directory/trunk/content: ./ api/user-guide/1-introduction.html api/user-guide/1.2-ldap-in-a-few-words.html

[bu...@apache.org]

Author: buildbot
Date: Sat Dec 31 01:00:39 2016
New Revision: 1003802

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/api/user-guide/1-introduction.html
    websites/staging/directory/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Dec 31 01:00:39 2016
@@ -1 +1 @@
-1776669
+1776670

Modified: websites/staging/directory/trunk/content/api/user-guide/1-introduction.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide/1-introduction.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/1-introduction.html Sat Dec 31 01:00:39 2016
@@ -185,12 +185,12 @@
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1 id="1-introduction">1 - Introduction<a class="headerlink" href="#1-introduction" title="Permanent link">&para;</a></h1>
 <p>This User Guide teaches developers how to use the Apache LDAP API. Throughout these documents, we have interspersed descriptions of features with snippets of code.  These code samples are used by our integration tests as well.</p>
-<p>Hopefully there's enough here to get you started -- quickly.  If you fee4l like improving this document or have questions / suggestions, please post to the Apache Directory LDAP API mailing list.  All code and doc contributions are welcomed!</p>
+<p>Hopefully there's enough here to get you started -- quickly.  If you feel like improving this document or have questions / suggestions, please post to the Apache Directory LDAP API mailing list.  All code and doc contributions are welcomed!</p>
 <h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="1.1-java-and-ldap.html">1.1 - Java and LDAP</a></li>
 <li><a href="1.2-ldap-in-a-few-words.html">1.2 - LDAP in a few words</a></li>
-<li><a href="1.3-apache-ldap-api-rational.html">1.3 - The Apache LDAP API rational</a></li>
+<li><a href="1.3-apache-ldap-api-rational.html">1.3 - The Apache LDAP API rationale</a></li>
 <li><a href="1.4-preparation-to-code.html">1.4 - Preparation to code</a></li>
 </ul>
 

Modified: websites/staging/directory/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.html Sat Dec 31 01:00:39 2016
@@ -187,12 +187,12 @@ h2:hover > .headerlink, h3:hover > .head
 <p><strong>LDAP</strong> is not a new technlology. It has been around since the 90's to mitigate complexities inherent in <strong>X.500</strong> usage. Its name refers to <strong>L</strong>ightweight <strong>D</strong>irectory <strong>A</strong>ccess <strong>P</strong>rotocol. Soon after the first standard was issued, the first full <em>LDAP</em> server was created and X.500 became obsolete.</p>
 <p>We'll use the term <strong>LDAP</strong> to represent the protocol and <strong>LDAP</strong> server to represent the server that implements it.</p>
 <h2 id="features">Features<a class="headerlink" href="#features" title="Permanent link">&para;</a></h2>
-<p>An <strong>LDAP</strong> server provides access to entries stored in a backend database. It provides a mechanism for fast searching and retrieval of entries. Its data structure is hierarchical, and uses a schema to manage the definition of the entry's data formats.</p>
+<p>The <strong>LDAP</strong> protocol provides access to entries stored in a <strong>LDAP Server's</strong> database. It provides the mechanism for fast searching and retrieval of entries. Its data structures are hierarchical, and uses a schema to manage the definition of a particular entry's data formats.</p>
 <p>An <strong>LDAP</strong> client must first connect to a server and disconnect when finished. Some operations may be performed on the data itself, e.g. searches, modifications and deletions, along with a few others.</p>
-<p><strong>LDAP</strong> servers are extensible, but they all use a common protocol which makes it easy for users to request to interact with them. This API is an example of what <strong>LDAP</strong> is good at: fast data access across servers.</p>
+<p><strong>LDAP</strong> servers are extensible, but they all use a common protocol which makes it easy for users to request to interact with them, in a way that isn't tied to a particular vendor's implementation. This API is an example of what <strong>LDAP</strong> is good at: fast data access across servers of all types.</p>
 <h2 id="characteristics">Characteristics<a class="headerlink" href="#characteristics" title="Permanent link">&para;</a></h2>
-<p><strong>LDAP</strong> servers are fast for retrievals, having been designed specifically for this purpose. But modifications are costly. These characteristics must be understood when writing applications that use an <strong>LDAP</strong> server for data storage.</p>
-<p>Each entry is associated with a location within its corresponding <strong>D</strong>irectory <strong>I</strong>nformation <strong>T</strong>ree, and we use what is known as a <strong>D</strong>istinguished <strong>N</strong>ame (or <strong>Dn</strong>) to describe this address. The base entry is known as the suffix, and all entries beneath it are collectively known as its <strong>DIT</strong>.</p>
+<p><strong>LDAP</strong> servers are fast for retrievals, having been designed specifically for this purpose. But modifications can be costly. These characteristics must be understood when writing applications that use an <strong>LDAP</strong> server for data storage.</p>
+<p>Each entry is associated with a location within its corresponding <strong>D</strong>irectory <strong>I</strong>nformation <strong>T</strong>ree, and we use what is known as a <strong>D</strong>istinguished <strong>N</strong>ame (or <strong>Dn</strong>) to describe this address. The base entry is known as the suffix, it along with all entries beneath it are collectively known as the <strong>DIT</strong>.</p>
 <h2 id="programming">Programming<a class="headerlink" href="#programming" title="Permanent link">&para;</a></h2>
 <p><strong>LDAP</strong> is a part of the <strong>IT</strong> landscape and so it's necessary to learn how to deal with it. <strong>LDAP</strong> servers are used to manage authentications, authorizations, demographic information about users and more. It's very likely that you will have to write some code to access data with <strong>LDAP</strong> at some point, and existing <strong>API</strong>s aren't quite up to the task. This <strong>LDAP API</strong> has been designed to simplify usage and ensure proper interaction with the server.</p>
 <h2 id="going-further">Going further<a class="headerlink" href="#going-further" title="Permanent link">&para;</a></h2>