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

[bu...@apache.org]

Author: buildbot
Date: Sat Dec 31 03:15:39 2016
New Revision: 1003811

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    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 03:15:39 2016
@@ -1 +1 @@
-1776681
+1776682

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 03:15:39 2016
@@ -189,7 +189,7 @@ h2:hover > .headerlink, h3:hover > .head
 <h2 id="features">Features<a class="headerlink" href="#features" title="Permanent link">&para;</a></h2>
 <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 data formats allowed accross those entries.</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 simplifies application access 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>
+<p><strong>LDAP</strong> servers are extensible, but they all use a common protocol providing access to the data in a way that isn't tied to a particular vendor's implementation.</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 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.  The suffix along with all entries beneath it are collectively known as the <strong>DIT</strong>.</p>