svn commit: r1003799 - 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 00:42:39 2016
New Revision: 1003799

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 00:42:39 2016
@@ -1 +1 @@
-1776667
+1776668

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 00:42:39 2016
@@ -192,9 +192,9 @@ h2:hover > .headerlink, h3:hover > .head
 <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>
 <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 it's corresponding <strong>D</strong>irectory <strong>I</strong>nformation <strong>T</strong>ree, and we use what's called 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>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>
 <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 unavoidable that we must deal with it. <strong>LDAP</strong> servers are used to manage authentication, authorizations, demographic info and more. It's very likely that you will have to write some code to access data over <strong>LDAP</strong>, and existing <strong>API</strong>s aren't quite up to the task. This <strong>LDAP API</strong> has been designed to simplify usage.</p>
+<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>