directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From smckin...@apache.org
Subject svn commit: r1776821 - in /directory/site/trunk/content/api/user-guide: 1.2-ldap-in-a-few-words.mdtext 1.3-apache-ldap-api-rational.mdtext
Date Sun, 01 Jan 2017 00:18:44 GMT
Author: smckinney
Date: Sun Jan  1 00:18:44 2017
New Revision: 1776821

URL: http://svn.apache.org/viewvc?rev=1776821&view=rev
Log:
fm

Modified:
    directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext
    directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext

Modified: directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext?rev=1776821&r1=1776820&r2=1776821&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext Sun Jan  1
00:18:44 2017
@@ -29,7 +29,7 @@ Notice: Licensed to the Apache Software
 We'll use the term **LDAP** to represent the protocol and **LDAP server** to represent the
server that implements it.
 
 ## Features
-The **LDAP** protocol provides access to entries stored in a **LDAP Server's** 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.
+The **LDAP** protocol provides access to entries stored in a **LDAP Server's** 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 across
those entries.
 
 An **LDAP** 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.
 

Modified: directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext?rev=1776821&r1=1776820&r2=1776821&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext Sun Jan
 1 00:18:44 2017
@@ -24,20 +24,20 @@ Notice: Licensed to the Apache Software
 
 # 1.3 - The Apache LDAP API rationale
 
-When contemplating creating a new Java API for **LDAP** usage, we needed to consider whether
this is a duplication of effort, as there were already in existence a number of libraries.
For example:
+When contemplating the creation of a new Java API for **LDAP**, we needed to first consider
whether it was really necessary, because there were already a number of libraries that did
it. For example:
 
 * **JNDI** : the default **JDK** **API**
 * **Netscape** (a.k.a Mozilla) [LdapSdk](http://www-archive.mozilla.org/directory/javasdk.html)
 * **OpenLDAP** [JLdap](http://www.openldap.org/jldap/)
 
-So what makes the development of our new *LDAP JAVA API* a valid effort and not another example
of the **[NIH](http://en.wikipedia.org/wiki/Not_Invented_Here)** syndrome?
+So why is the development of our new *LDAP API* for Java NOT the **[NIH](http://en.wikipedia.org/wiki/Not_Invented_Here)**
syndrome?
 
-There are many reasons and we'll discuss them throughout this chapter.
+There are a number of reasons for which we'll discuss throughout this chapter.
 
 ## History
-The Apache Directory Server project was started using the **JNDI** library, but many of its
**LDAP** structures were developed in-house because **JNDI** was ineffective for interacting
with **LDAP** directories.  It wasn't convenient for us to use JNDI which means it won't be
for you either.  Eventually, all of the necessary **LDAP** data structures (_Attribute_, _Entry_,
_DN_, ...) were implemented again by us.
+The Apache Directory Server project was started using the **JNDI** library, but many of its
**LDAP** structures had to be developed in-house because the **JNDI** library was ineffective
for interacting with an **LDAP** server.  It wasn't convenient for us to use JNDI which means
it won't be for you either.  Eventually, all of the necessary **LDAP** data structures (_Attribute_,
_Entry_, _DN_, ...) were re-implemented by us.
 
-At some point we needed to communicate with other **LDAP** servers without using the **JNDI**
library, so we developed our own _LdapConnection_ class. This was the first step toward a
full **Java API** specifically designed for LDAP usage on the Java platform.
+At some point we had to communicate with other **LDAP** servers without using the **JNDI**
library, so we developed our own _LdapConnection_ class. This was the first step toward a
full **Java API** specifically designed for LDAP usage on the Java platform.
 
 Strangely, after starting this effort (back in 2007), some people from **Sun** (Microsystems),
who was working on the **OpenDS** project, contacted us to ask if we'd be interested in helping
them create the next version of **JNDI**. ([Resurrecting The Java LDAP Centric API](https://blogs.oracle.com/treydrake/entry/resurrecting_the_java_ldap_centric).
Sadly this effort stalled, as the need for *JNDI2* was no longer a priority for **Sun**. Nevertheless
we decided to continue our work but the the pace was slow.
 



Mime
View raw message