directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1036899 - in /websites/staging/directory/trunk/content: ./ api/user-guide/1.3-apache-ldap-api-rational.html
Date Tue, 13 Nov 2018 14:35:33 GMT
Author: buildbot
Date: Tue Nov 13 14:35:33 2018
New Revision: 1036899

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    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 Tue Nov 13 14:35:33 2018
@@ -1 +1 @@
-1846458
+1846516

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
Tue Nov 13 14:35:33 2018
@@ -200,7 +200,7 @@ h2:hover > .headerlink, h3:hover > .head
 <h2 id="history">History<a class="headerlink" href="#history" title="Permanent link">&para;</a></h2>
 <p>The Apache Directory Server project was started using the <strong>JNDI</strong>
library, but many of its <strong>LDAP</strong> structures had to be developed
in-house because the <strong>JNDI</strong> library was ineffective for interacting
with an <strong>LDAP</strong> server.  It wasn't convenient for us to use JNDI
which means it won't be for you either.  Eventually, all of the necessary <strong>LDAP</strong>
data structures (<em>Attribute</em>, <em>Entry</em>, <em>DN</em>,
...) were re-implemented by us.</p>
 <p>At some point we had to communicate with other <strong>LDAP</strong>
servers without using the <strong>JNDI</strong> library, 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 on the Java platform.</p>
-<p>Strangely, after starting this effort (back in 2007), some people from <strong>Sun</strong>
(Microsystems), who was 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>Strangely, after starting this effort (back in 2007), some people from <strong>Sun</strong>
(Microsystems), who was 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 once again after
<strong>Oracle</strong> bought <strong>Sun</strong> in 2010, and its
project team disbanded.</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 be capable of doing. We agreed on
these key features for the new <strong>LDAP API</strong>:</p>
 <ul>



Mime
View raw message