svn commit: r1003810 - 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:13:07 2016
New Revision: 1003810

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:13:07 2016
@@ -1 +1 @@
-1776680
+1776681

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:13:07 2016
@@ -185,18 +185,18 @@
 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="12-ldap-in-a-few-words">1.2 - LDAP in a few words<a class="headerlink" href="#12-ldap-in-a-few-words" title="Permanent link">&para;</a></h1>
 <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>
+<p>We'll use the term <strong>LDAP</strong> to represent the protocol and <strong>LDAP server</strong> to represent the server that implements it.</p>
 <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 a particular 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 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 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>
+<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>
 <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, it along with all entries beneath it are collectively known as the <strong>DIT</strong>.</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>
 <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>
-<p>This was a very short introduction, there's more literature about <strong>LDAP</strong> on the web : <a href="http://en.wikipedia.org/wiki/LDAP">Wikipedia</a> provides a good starting point.</p>
+<p>This was a short introduction, there's more literature about <strong>LDAP</strong> on the web : <a href="http://en.wikipedia.org/wiki/LDAP">Wikipedia</a> provides a good starting point.</p>
 
 
     <div class="nav">