You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by bu...@apache.org on 2016/12/31 00:54:33 UTC
svn commit: r1003800 - in /websites/staging/directory/trunk/content: ./
api/user-guide/1.2-ldap-in-a-few-words.html
api/user-guide/1.3-apache-ldap-api-rational.html
Author: buildbot
Date: Sat Dec 31 00:54:33 2016
New Revision: 1003800
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
websites/staging/directory/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.html
Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Dec 31 00:54:33 2016
@@ -1 +1 @@
-1776668
+1776669
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:54:33 2016
@@ -165,7 +165,7 @@
</div>
<div class="nav_next">
- <a href="1.3-apache-ldap-api-rational.html">1.3 - The Apache LDAP API rational</a>
+ <a href="1.3-apache-ldap-api-rational.html">1.3 - The Apache LDAP API rationale</a>
</div>
<div class="clearfix"></div>
@@ -212,7 +212,7 @@ h2:hover > .headerlink, h3:hover > .head
</div>
<div class="nav_next">
- <a href="1.3-apache-ldap-api-rational.html">1.3 - The Apache LDAP API rational</a>
+ <a href="1.3-apache-ldap-api-rational.html">1.3 - The Apache LDAP API rationale</a>
</div>
<div class="clearfix"></div>
Modified: websites/staging/directory/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.html Sat Dec 31 00:54:33 2016
@@ -184,20 +184,20 @@
}
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="13-the-apache-ldap-api-rationale">1.3 - The Apache LDAP API rationale<a class="headerlink" href="#13-the-apache-ldap-api-rationale" title="Permanent link">¶</a></h1>
-<p>When creating a new <strong>LDAP</strong> <strong>API</strong>, we need to consider whether it's a duplication of effort; there are already some libraries that do this. For example:</p>
+<p>When creating this new <strong>LDAP</strong> <strong>API</strong>, we needed to consider whether we're duplicating effort as there were already a few libraries that can do this in Java. For example:</p>
<ul>
<li><strong>JNDI</strong> : the default <strong>JDK</strong> <strong>API</strong></li>
<li><strong>Netscape</strong> (a.k.a Mozilla) <a href="http://www.mozilla.org/directory/javasdk.html">LdapSdk</a></li>
<li><strong>OpenLDAP</strong> <a href="http://www.openldap.org/jldap/">JLdap</a></li>
</ul>
-<p>What makes the development of this new <em>LDAP JAVA API</em> a valid effort, and <strong><a href="http://en.wikipedia.org/wiki/Not_Invented_Here">NIH</a></strong> syndrom?</p>
-<p>There are many reasons why we decided to start to work on this <strong>API</strong>, and we'll discuss them throughout this chapter.</p>
+<p>So what makes the development of this new <em>LDAP JAVA API</em> a valid effort and another example of the <strong><a href="http://en.wikipedia.org/wiki/Not_Invented_Here">NIH</a></strong> syndrome?</p>
+<p>There are many reasons why we decided to start working on this <strong>API</strong> and we'll discuss them throughout this chapter.</p>
<h2 id="history">History<a class="headerlink" href="#history" title="Permanent link">¶</a></h2>
-<p>The Apache Directory Server project was first using <strong>JNDI</strong>, but many of the internal <strong>LDAP</strong> structures were developed internally, because <strong>JNDI</strong> was not well suited for <strong>LDAP</strong> usage. This meant it wasn't convenient for us to use these structures. Step by step, all of the <strong>LDAP</strong> objects (<em>Attribute</em>, <em>Entry</em>, <em>DN</em>, ...) were implemented again.</p>
-<p>At some point, we needed to communicate with other <strong>LDAP</strong> servers without having using <strong>JNDI</strong>, so we developed our own <em>LdapConnection</em> class. This was the first step toward a full <strong>Java API</strong> specifically designed for LDAP.</p>
-<p>Strangely enough when we were doing this, back in 2007, <strong>Sun</strong> people working on the <strong>OpenDS</strong> project contacted us to ask if we'd be interested in helping them with the next version of <strong>JNDI</strong> (<a href="https://blogs.oracle.com/treydrake/entry/resurrecting_the_java_ldap_centric">Resurrecting The Java LDAP Centric API</a>. Sadly, this effort stalled, as the need for <em>JNDI2</em> was no longer a priority for <strong>Sun</strong>. We decided to continue with our work but the the pace was slow.</p>
-<p>The work began once again after the <strong>OpenDS</strong> project team's presentation at <strong>LdapCon</strong> back in 2009 (<a href="http://www.symas.com/ldapcon2009/papers/poitou1.shtml">Towards a common LDAP API for the Java Platform</a>). The story repeated itself after <strong>Oracle</strong> bought <strong>Sun</strong> in 2010.</p>
-<p>Despite these fits and starts, a consensus was reached on the need for a new <strong>API</strong> and what it should do. We agreed on the key features for a new <strong>LDAP API</strong>:</p>
+<p>The Apache Directory Server project was started using the <strong>JNDI</strong> library, but many of its <strong>LDAP</strong> structure usages were developed in-house because <strong>JNDI</strong> wasn't well suited for <strong>LDAP</strong> directories. It wasn't convenient to use JNDI (which means it won't be for you either). Eventually all of the <strong>LDAP</strong> objects (<em>Attribute</em>, <em>Entry</em>, <em>DN</em>, ...) were implemented again by us.</p>
+<p>At some point we needed to communicate with other <strong>LDAP</strong> servers without <strong>JNDI</strong>, so we developed our own <em>LdapConnection</em> class. This was the first step toward a full <strong>Java API</strong> specifically designed for LDAP usage.</p>
+<p>Strangely enough as we were doing this, back in 2007, Some people from <strong>Sun</strong> Microsystems, working on the <strong>OpenDS</strong> project, contacted us to ask if we'd be interested in helping them create the next version of <strong>JNDI</strong> (<a href="https://blogs.oracle.com/treydrake/entry/resurrecting_the_java_ldap_centric">Resurrecting The Java LDAP Centric API</a>. Sadly this effort stalled, as the need for <em>JNDI2</em> was no longer a priority for <strong>Sun</strong>. Nevertheless we decided to continue our work but the the pace was slow.</p>
+<p>The work renewed after the <strong>OpenDS</strong> project team's presentation at <strong>LdapCon</strong> in 2009 (<a href="http://www.symas.com/ldapcon2009/papers/poitou1.shtml">Towards a common LDAP API for the Java Platform</a>). The story repeated itself after <strong>Oracle</strong> bought <strong>Sun</strong> in 2010.</p>
+<p>Despite these fits and starts, a consensus was reached about the need for a new LDAP <strong>API</strong> and what it should do. We agreed on these key features for the new <strong>LDAP API</strong>:</p>
<ul>
<li>A complete coverage of the <strong>LDAP</strong> protocol</li>
<li>A schema aware <strong>API</strong></li>
@@ -205,9 +205,9 @@ h2:hover > .headerlink, h3:hover > .head
<li>An <strong>API</strong> taking advantage of the new <strong>Java</strong> construction (generics, ellipsis, NIO)</li>
</ul>
<h2 id="result">Result<a class="headerlink" href="#result" title="Permanent link">¶</a></h2>
-<p>This newly defined <strong>API</strong> fulfills all of these aspects. </p>
-<p>We wanted to make sure this <strong>API</strong> was made available to the masses. The Apache Software Foundation values quality and community over code, which means the code is the result of a collaborative work, our users being a necessary part of this collaboration. Every bug a user finds, is an opportunity to provide a better version of the <strong>API</strong> for everyone.</p>
-<p>In the end, we're proud to deliver a useful <strong>API</strong> that everyone can use, include our own projects like the Apache Directory Server, Directory Studio and Fortress. </p>
+<p>Our newly defined <strong>API</strong> fulfills all of these aspects. </p>
+<p>We needed to ensure our <strong>LDAP API</strong> was made available to the masses. Because the Apache Software Foundation values community over code, this code was the result of collaboration, and our users are a necessary part of this process. Every time a user finds and reports a bug we have the opportunity to provide a better version of this <strong>API</strong> for everyone who uses it.</p>
+<p>In the end, we're proud to deliver a useful <strong>API</strong> that everyone can use, including our own projects like the Apache Directory Server, Directory Studio and Fortress. </p>
<div class="nav">