directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r836214 - in /websites/staging/directory/trunk/content: ./ contribute.html index.html issue-tracking.html mailing-lists-and-irc.html news.html original-project-proposal.html sources.html special-thanks.html team.html vision.html
Date Fri, 26 Oct 2012 06:53:40 GMT
Author: buildbot
Date: Fri Oct 26 06:53:39 2012
New Revision: 836214

Log:
Staging update by buildbot for directory

Added:
    websites/staging/directory/trunk/content/vision.html
Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/contribute.html
    websites/staging/directory/trunk/content/index.html
    websites/staging/directory/trunk/content/issue-tracking.html
    websites/staging/directory/trunk/content/mailing-lists-and-irc.html
    websites/staging/directory/trunk/content/news.html
    websites/staging/directory/trunk/content/original-project-proposal.html
    websites/staging/directory/trunk/content/sources.html
    websites/staging/directory/trunk/content/special-thanks.html
    websites/staging/directory/trunk/content/team.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Oct 26 06:53:39 2012
@@ -1 +1 @@
-1402391
+1402408

Modified: websites/staging/directory/trunk/content/contribute.html
==============================================================================
--- websites/staging/directory/trunk/content/contribute.html (original)
+++ websites/staging/directory/trunk/content/contribute.html Fri Oct 26 06:53:39 2012
@@ -85,7 +85,7 @@
         <li><a href="./articles.html">Articles</a></li>
         <li><a href="./conference-materials.html">Conferences</a></li>
         <li><a href="./testimonies.html">Testimonials</a></li>
-        <li><a href="./ldap-renaissance.html">Vision</a></li>
+        <li><a href="./vision.html">Vision</a></li>
         <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
         <li><a href="./sources.html">Sources</a></li>
         <li><a href="./issue-tracking.html">Issue Tracking</a></li>

Modified: websites/staging/directory/trunk/content/index.html
==============================================================================
--- websites/staging/directory/trunk/content/index.html (original)
+++ websites/staging/directory/trunk/content/index.html Fri Oct 26 06:53:39 2012
@@ -85,7 +85,7 @@
         <li><a href="./articles.html">Articles</a></li>
         <li><a href="./conference-materials.html">Conferences</a></li>
         <li><a href="./testimonies.html">Testimonials</a></li>
-        <li><a href="./ldap-renaissance.html">Vision</a></li>
+        <li><a href="./vision.html">Vision</a></li>
         <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
         <li><a href="./sources.html">Sources</a></li>
         <li><a href="./issue-tracking.html">Issue Tracking</a></li>

Modified: websites/staging/directory/trunk/content/issue-tracking.html
==============================================================================
--- websites/staging/directory/trunk/content/issue-tracking.html (original)
+++ websites/staging/directory/trunk/content/issue-tracking.html Fri Oct 26 06:53:39 2012
@@ -85,7 +85,7 @@
         <li><a href="./articles.html">Articles</a></li>
         <li><a href="./conference-materials.html">Conferences</a></li>
         <li><a href="./testimonies.html">Testimonials</a></li>
-        <li><a href="./ldap-renaissance.html">Vision</a></li>
+        <li><a href="./vision.html">Vision</a></li>
         <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
         <li><a href="./sources.html">Sources</a></li>
         <li><a href="./issue-tracking.html">Issue Tracking</a></li>

Modified: websites/staging/directory/trunk/content/mailing-lists-and-irc.html
==============================================================================
--- websites/staging/directory/trunk/content/mailing-lists-and-irc.html (original)
+++ websites/staging/directory/trunk/content/mailing-lists-and-irc.html Fri Oct 26 06:53:39
2012
@@ -85,7 +85,7 @@
         <li><a href="./articles.html">Articles</a></li>
         <li><a href="./conference-materials.html">Conferences</a></li>
         <li><a href="./testimonies.html">Testimonials</a></li>
-        <li><a href="./ldap-renaissance.html">Vision</a></li>
+        <li><a href="./vision.html">Vision</a></li>
         <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
         <li><a href="./sources.html">Sources</a></li>
         <li><a href="./issue-tracking.html">Issue Tracking</a></li>

Modified: websites/staging/directory/trunk/content/news.html
==============================================================================
--- websites/staging/directory/trunk/content/news.html (original)
+++ websites/staging/directory/trunk/content/news.html Fri Oct 26 06:53:39 2012
@@ -85,7 +85,7 @@
         <li><a href="./articles.html">Articles</a></li>
         <li><a href="./conference-materials.html">Conferences</a></li>
         <li><a href="./testimonies.html">Testimonials</a></li>
-        <li><a href="./ldap-renaissance.html">Vision</a></li>
+        <li><a href="./vision.html">Vision</a></li>
         <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
         <li><a href="./sources.html">Sources</a></li>
         <li><a href="./issue-tracking.html">Issue Tracking</a></li>

Modified: websites/staging/directory/trunk/content/original-project-proposal.html
==============================================================================
--- websites/staging/directory/trunk/content/original-project-proposal.html (original)
+++ websites/staging/directory/trunk/content/original-project-proposal.html Fri Oct 26 06:53:39
2012
@@ -85,7 +85,7 @@
         <li><a href="./articles.html">Articles</a></li>
         <li><a href="./conference-materials.html">Conferences</a></li>
         <li><a href="./testimonies.html">Testimonials</a></li>
-        <li><a href="./ldap-renaissance.html">Vision</a></li>
+        <li><a href="./vision.html">Vision</a></li>
         <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
         <li><a href="./sources.html">Sources</a></li>
         <li><a href="./issue-tracking.html">Issue Tracking</a></li>

Modified: websites/staging/directory/trunk/content/sources.html
==============================================================================
--- websites/staging/directory/trunk/content/sources.html (original)
+++ websites/staging/directory/trunk/content/sources.html Fri Oct 26 06:53:39 2012
@@ -85,7 +85,7 @@
         <li><a href="./articles.html">Articles</a></li>
         <li><a href="./conference-materials.html">Conferences</a></li>
         <li><a href="./testimonies.html">Testimonials</a></li>
-        <li><a href="./ldap-renaissance.html">Vision</a></li>
+        <li><a href="./vision.html">Vision</a></li>
         <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
         <li><a href="./sources.html">Sources</a></li>
         <li><a href="./issue-tracking.html">Issue Tracking</a></li>

Modified: websites/staging/directory/trunk/content/special-thanks.html
==============================================================================
--- websites/staging/directory/trunk/content/special-thanks.html (original)
+++ websites/staging/directory/trunk/content/special-thanks.html Fri Oct 26 06:53:39 2012
@@ -85,7 +85,7 @@
         <li><a href="./articles.html">Articles</a></li>
         <li><a href="./conference-materials.html">Conferences</a></li>
         <li><a href="./testimonies.html">Testimonials</a></li>
-        <li><a href="./ldap-renaissance.html">Vision</a></li>
+        <li><a href="./vision.html">Vision</a></li>
         <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
         <li><a href="./sources.html">Sources</a></li>
         <li><a href="./issue-tracking.html">Issue Tracking</a></li>

Modified: websites/staging/directory/trunk/content/team.html
==============================================================================
--- websites/staging/directory/trunk/content/team.html (original)
+++ websites/staging/directory/trunk/content/team.html Fri Oct 26 06:53:39 2012
@@ -85,7 +85,7 @@
         <li><a href="./articles.html">Articles</a></li>
         <li><a href="./conference-materials.html">Conferences</a></li>
         <li><a href="./testimonies.html">Testimonials</a></li>
-        <li><a href="./ldap-renaissance.html">Vision</a></li>
+        <li><a href="./vision.html">Vision</a></li>
         <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
         <li><a href="./sources.html">Sources</a></li>
         <li><a href="./issue-tracking.html">Issue Tracking</a></li>

Added: websites/staging/directory/trunk/content/vision.html
==============================================================================
--- websites/staging/directory/trunk/content/vision.html (added)
+++ websites/staging/directory/trunk/content/vision.html Fri Oct 26 06:53:39 2012
@@ -0,0 +1,224 @@
+<!DOCTYPE html>
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+<html>
+	<head>
+		<title>Vision &mdash; Apache Directory</title>
+		
+		<link href="./css/common.css" rel="stylesheet" type="text/css">
+		<link href="./css/green.css" rel="stylesheet" type="text/css">
+	
+	</head>
+	<body>
+	    <div id="container">
+            <div id="header">
+                <div id="subProjectsNavBar">
+                    <a href="./">
+                        
+                        <STRONG>Apache Directory Project</STRONG>
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./apacheds">
+                        
+                        ApacheDS
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./studio">
+                        
+                        Apache Directory Studio
+                        
+                    </a>
+                    &nbsp;|&nbsp;
+                    <a href="./api">
+                        
+                        Apache LDAP API
+                        
+                    </a>
+                </div><!-- subProjectsNavBar -->
+            </div><!-- header -->
+            <div id="content">
+                <div id="leftColumn">
+                    
+<div id="navigation">
+    
+    <h5>Latest News</h5>
+    <ul>
+        <li><a href="./#news">ApacheDS</a></li>
+        <li><a href="./studio/#news">Apache Directory Studio</a></li>
+        <li><a href="./api/#news">Apache LDAP API</a></li>
+    </ul>
+    <h5>Latest Downloads</h5>
+    <ul>
+        <li><a href="./apacheds/2.0/downloads.html">ApacheDS 2.0.0-M8</a>&nbsp;&nbsp;<IMG
src="http://directory.apache.org/staticresources/images/new_badge.gif" alt="" style="margin-bottom:-3px;"
border="0"></li>
+        <li><a href="./studio/2.0/download/">Studio 2.0 M3</a>&nbsp;&nbsp;<IMG
src="http://directory.apache.org/staticresources/images/new_badge.gif" alt="" style="margin-bottom:-3px;"
border="0"></li>
+        <li><a href="./studio/downloads.html">Studio 1.5.3</a></li>
+        <li><a href="./api/downloads.html">LDAP API 1.0.0-M13</a>&nbsp;&nbsp;<IMG
src="http://directory.apache.org/staticresources/images/new_badge.gif" alt="" style="margin-bottom:-3px;"
border="0"></li>
+    </ul>
+    <h5>Sub-Projects</h5>
+    <ul>
+        <li><a href="./apacheds/">ApacheDS</a></li>
+        <li><a href="./studio/">Apache Directory Studio</a></li>
+        <li><a href="./api/">Apache LDAP API</a></li>
+    </ul>
+    <h5>Sandbox</h5>
+    <ul>
+        <li><a href="./triplesec/">Triplesec</a></li>
+    </ul>
+    <h5>Resources</h5>
+    <ul>
+        <li><a href="./articles.html">Articles</a></li>
+        <li><a href="./conference-materials.html">Conferences</a></li>
+        <li><a href="./testimonies.html">Testimonials</a></li>
+        <li><a href="./vision.html">Vision</a></li>
+        <li><a href="./mailing-lists-and-irc.html">Mailing Lists &amp; IRC</a></li>
+        <li><a href="./sources.html">Sources</a></li>
+        <li><a href="./issue-tracking.html">Issue Tracking</a></li>
+    </ul>
+    
+    
+    <h5>Community</h5>
+    <ul>
+        <li><a href="./contribute.html">How to Contribute</a></li>
+        <li><a href="./team.html">Team</a></li>
+        <li><a href="./original-project-proposal.html">Original Project Proposal</a></li>
+        <li><a href="./special-thanks.html" class="external-link" rel="nofollow">Special
Thanks</a></li>
+    </ul>
+    <h5>About Apache</h5>
+    <ul>
+        <li><a href="http://www.apache.org/">Apache</a></li>
+        <li><a href="http://www.apache.org/licenses/">License</a></li>
+        <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+        <li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+        <li><a href="http://www.apache.org/security/">Security</a></li>
+    </ul>
+    
+</div><!-- navigation -->
+
+                </div><!-- leftColumn -->
+                <div id="rightColumn">
+
+
+
+<h1 id="architecting-the-modern-ldap-renaissance-the-apache-directory-vision">Architecting
the Modern LDAP Renaissance: The Apache Directory Vision</h1>
+<p>by Alex Karasulu, Founder of the <a href="http://directory.apache.org">Apache
Directory Project</a>, October 2002
+This paper was later, in September 2007, submitted to and accepted by the <a href="http://www.guug.de/veranstaltungen/ldapcon2007/">1st
International Conference on LDAP</a>, Cologne (Germany)
+[TOC]</p>
+<h2 id="abstract">Abstract</h2>
+<div class="codehilite"><pre><span class="n">Directory</span> <span
class="n">technology</span> <span class="n">is</span> <span class="n">an</span>
<span class="n">indivisible</span> <span class="n">cornerstone</span>
<span class="n">in</span> <span class="n">computing</span> <span
class="n">science</span> <span class="ow">and</span> <span class="n">LDAP</span>
<span class="n">specifically</span> <span class="n">is</span> <span
class="n">essential</span> <span class="n">in</span> 
+<span class="n">several</span> <span class="n">industries</span>
<span class="n">however</span> <span class="n">it</span> <span
class="n">is</span> <span class="n">severely</span> <span class="n">underutilized</span><span
class="o">.</span>
+
+<span class="n">One</span> <span class="n">would</span> <span
class="n">expect</span> <span class="n">the</span> <span class="n">demand</span>
<span class="k">for</span> <span class="n">LDAP</span> <span class="n">to</span>
<span class="n">increase</span> <span class="n">as</span> <span
class="n">infrastructures</span> <span class="ow">and</span> <span
class="n">the</span> <span class="n">Internet</span> <span class="n">grow</span><span
class="p">,</span> <span class="n">with</span> <span class="n">more</span>
<span class="n">boundaries</span><span class="p">,</span> 
+<span class="n">nodes</span><span class="p">,</span> <span class="n">services</span><span
class="p">,</span> <span class="n">users</span> <span class="ow">and</span>
<span class="n">ways</span> <span class="n">of</span> <span class="n">doing</span>
<span class="n">business</span> <span class="n">emerging</span> <span
class="n">rapidly</span><span class="o">.</span> <span class="n">Directories</span>
<span class="n">inherently</span> <span class="n">solve</span> <span
class="n">integration</span> 
+<span class="n">problems</span> <span class="n">yet</span> <span
class="n">more</span> <span class="n">integration</span> <span class="n">problems</span>
<span class="n">appear</span> <span class="k">while</span> <span
class="n">complexities</span> <span class="n">of</span> <span class="n">existing</span>
<span class="n">problems</span> <span class="n">are</span> <span
class="n">compounded</span><span class="o">.</span> <span class="n">We</span><span
class="err">&#39;</span><span class="n">re</span> <span class="ow">not</span>

+<span class="n">witnessing</span> <span class="n">a</span> <span
class="n">proportional</span> <span class="n">increase</span> <span
class="n">in</span> <span class="n">the</span> <span class="n">adoption</span>
<span class="n">rate</span> <span class="n">of</span> <span class="n">directories</span><span
class="p">;</span> <span class="n">namely</span> <span class="n">LDAP</span>
<span class="n">directories</span><span class="o">.</span> <span
class="n">This</span> <span class="n">is</span> <span class="ow">not</span>
<span class="n">a</span> 
+<span class="n">coincidence</span><span class="o">.</span>
+
+<span class="n">It</span> <span class="n">is</span> <span class="n">the</span>
<span class="n">result</span> <span class="n">of</span> <span class="n">a</span>
<span class="n">lack</span> <span class="n">of</span> <span class="n">several</span>
<span class="n">factors:</span> <span class="n">tooling</span> <span
class="n">support</span><span class="p">,</span> <span class="n">courses</span>
<span class="n">on</span> <span class="n">directory</span> <span
class="n">technology</span> <span class="n">in</span> <span class="n">academia</span><span
class="p">,</span> 
+<span class="n">qualified</span> <span class="n">domain</span> <span
class="n">experts</span> <span class="ow">and</span> <span class="n">rich</span>
<span class="n">integration</span> <span class="n">constructs</span><span
class="o">.</span> <span class="n">More</span> <span class="n">specifically</span><span
class="p">,</span> <span class="n">information</span> <span class="n">architects</span>
<span class="ow">and</span> <span class="n">key</span> 
+<span class="n">decision</span> <span class="n">makers</span> <span
class="n">incorrectly</span> <span class="n">choose</span> <span class="n">to</span>
<span class="n">apply</span> <span class="n">ad</span> <span class="n">hoc</span>
<span class="n">solutions</span> <span class="n">to</span> <span
class="n">problems</span> <span class="n">rather</span> <span class="n">than</span>
<span class="n">opting</span> <span class="n">to</span> <span class="n">using</span>
<span class="n">directories</span><span class="o">.</span>
+
+<span class="n">If</span> <span class="n">these</span> <span class="n">limitations</span>
<span class="n">are</span> <span class="n">removed</span> <span
class="k">then</span> <span class="n">there</span> <span class="n">would</span>
<span class="n">be</span> <span class="n">greater</span> <span
class="n">comfort</span><span class="p">,</span> <span class="n">flexibility</span>
<span class="ow">and</span> <span class="n">adoption</span><span
class="o">.</span> <span class="n">LDAP</span> <span class="n">could</span>
<span class="k">do</span> 
+<span class="n">more</span> <span class="n">than</span> <span
class="n">it</span> <span class="n">does</span> <span class="n">today</span>
<span class="n">namely</span> <span class="n">in</span> <span class="n">the</span>
<span class="n">area</span> <span class="n">of</span> <span class="n">provisioning</span>
<span class="ow">and</span> <span class="n">workflow</span><span
class="o">.</span>
+
+<span class="n">LDAP</span> <span class="n">could</span> <span
class="n">potentially</span> <span class="n">experience</span> <span
class="n">a</span> <span class="n">Renaissance</span> <span class="n">with</span>
<span class="n">renewed</span> <span class="n">interest</span> <span
class="n">due</span> <span class="n">to</span> <span class="n">increased</span>
<span class="n">demand</span> <span class="n">to</span> <span class="n">solve</span>
<span class="n">the</span> 
+<span class="n">classical</span> <span class="n">integration</span>
<span class="n">problems</span> <span class="n">it</span> <span
class="n">was</span> <span class="n">designed</span> <span class="k">for</span>
<span class="ow">and</span> <span class="n">beyond</span><span
class="o">.</span>
+
+<span class="n">We</span> <span class="n">discuss</span> <span
class="n">these</span> <span class="n">limitations</span><span class="p">,</span>
<span class="ow">and</span> <span class="n">the</span> <span class="n">proposed</span>
<span class="n">means</span> <span class="n">to</span> <span class="n">remove</span>
<span class="n">them</span><span class="p">,</span> <span class="n">all</span>
<span class="n">in</span> <span class="n">an</span> <span class="n">effort</span>
<span class="n">to</span> <span class="n">express</span> <span
class="k">our</span> <span class="n">vision</span> 
+<span class="n">at</span> <span class="n">the</span> <span class="n">Apache</span>
<span class="n">Directory</span> <span class="n">Project</span><span
class="o">.</span> <span class="n">Our</span> <span class="n">aim</span>
<span class="n">is</span> <span class="n">clear</span><span class="p">;</span>
<span class="n">we</span> <span class="n">intend</span> <span class="n">to</span>
<span class="n">influence</span> <span class="ow">and</span> <span
class="n">incite</span> <span class="n">other</span> <span class="n">directory</span>

+<span class="n">implementers</span> <span class="ow">and</span> <span
class="n">projects</span> <span class="n">by</span> <span class="k">our</span>
<span class="n">example</span> <span class="n">to</span> <span
class="n">trigger</span> <span class="n">what</span> <span class="n">we</span>
<span class="n">envision</span> <span class="n">as</span> <span
class="n">the</span> <span class="n">Modern</span> <span class="n">LDAP</span>
<span class="n">Renaissance</span><span class="o">.</span>
+</pre></div>
+
+
+<h2 id="drivers-leading-to-the-birth-of-the-directory">Drivers Leading to the Birth
of the Directory</h2>
+<p>Several systems slowly appeared in the arsenal of tools used daily by those within
and across organizations. Data architects quickly could characterized two logical categories
of information spanning across all domains:</p>
+<ul>
+<li>Static information shared across applications and systems read frequently yet seldom
altered.</li>
+<li>Information specific to an event within an application (a transaction) read infrequently
however written rapidly in volume (data seldom accessed by external systems).</li>
+</ul>
+<p>The Directory relates to this first type of data above which has the following general
properties:</p>
+<ul>
+<li>Accessed by many clients</li>
+<li>Partitioned across different locations in different organizations owned by separate
authorities</li>
+<li>Structure data elements with data types (syntaxes) with semantics for matching</li>
+<li>Data easily fits into hierarchies</li>
+<li>Highly cross referenced</li>
+</ul>
+<p>The telecommunication industry in Europe, in particular, felt this burden while
managing shared information, specifically subscriber directories. Telephone companies in Europe,
some national providers and other international providers, managed profiles for subscribers,
a subset of which, needed to be published for public access.</p>
+<p>The ITU responded with the X.500 series of specifications. The Directory specifications
addressed these specific concerns for accessing information shared across organizations, located
in separate stores and managed by several different authorities. The access model and authoritative
model enabled organizations to publish subscriber information and allow others to access it
while delegating the management of access control, schema and other aspects to the proper
authorities. As a standard it was way ahead of its time.</p>
+<p>The X.500 specifications reveal a unique data access and authoritative model designed
specifically for the category of static shared data we defined above. It is a cornerstone
technology as is the relational database for the second category.</p>
+<h2 id="demand-for-directories-should-be-high">Demand for Directories Should Be High</h2>
+<p>Directories expose a unique model for efficiently accessing relatively static information
shared across multiple systems. Directory protocol designers intended the protocol to address
a class of specific problems through a standard means to access shared information centrally
while providing high availability. Existing storage paradigms failed to solve these problems
due to inherent limitations in their design.</p>
+<p>These data management problems fall under the domain of data integration. To integrate
systems one must integrate both the data and the processes. Interoperating systems often need
to access the same information however many systems simply duplicate that information (in
relational databases) rather than accessing it from a centralized service (the directory).
As a result multiple copies of the same information exist across these systems. Data synchronization
technologies emerged to address these issues of duplication such as meta-directories (not
real directories). These technologies never really solved all the issues of data duplication:
they merely facilitated the export, transformation and import of data across systems. The
serious issue of determining the authoritative copy still remained.</p>
+<p>For some time, commercial entities avoided addressing these integration problems
by centralizing access to this shared information. The market fueled the push of OLTP systems
since the transaction equated to money. As markets became saturated as several competitors
appeared, businesses started focusing on gains through efficiency. To streamline development
and maintenance better integration was needed while allowing transactions to span across interoperating
systems. This increased the need for directories.</p>
+<p>Aspects of growth naturally contribute to the demand for Directory technologies.
As the number of users, organizations, systems, services and machines expand the problems
of integration only increase without applying the correct remedy. In fact, the vast majority
of today's problems are primary integration problems. Hence one would expect the utilization
of Directories to increase proportionally with the increased demand. Unfortunately, a proportional
increase in demand for Directories has not been observed.</p>
+<h2 id="barriers-of-adoption">Barriers of Adoption</h2>
+<p>Although Directories, namely LDAP Directories, have proliferated over the past two
decades, their adoption has not been commensurate with the demand one would expect. Several
factors may be attributed to this less than optimal adoption rate.</p>
+<p>Directories still feel alien to most developers. Many admit, in theory, to a directory
as the ideal access model for shared information in their applications however most fall back
to using a relational database instead. Why?</p>
+<p>First there is no formal education around directory technologies while several courses
around relational database systems exist. This might explain in part why developers are much
more comfortable with keeping their Directory information stored and accessed from an RDBMS.
As a result, finding qualified Directory experts is difficult. Every generalist knows how
to use an RDBMS, yet costly specialists are needed to design, operate and maintain directories.
The cost and availability of specialized engineers factor into design decisions especially
if the process is formally conducted.</p>
+<p>Developers may also fall back to using an RDBMS instead of a Directory because of
a lack of rich integration tier constructs (like triggers, views and stored procedures). These
very useful constructs are missing in Directories yet have been available in relational databases
for decades. Today's heavy integration needs demand these constructs. For example the demand
for the event driven provisioning of information could be elegantly solved using triggers
and stored procedures as entries are added, updated and deleted. Data architects and developers
in this respect have been left in the dark-ages with LDAP while the RDBMS has given them what
they wanted/needed at the price of compounding their problems with data duplication.</p>
+<p>Perhaps the most significant factor driving these faulty decisions is the lack of
LDAP tooling. There are myriads of RDBMS tools for various aspects: tuning, accessing, and
designing. Tools for the RDBMS appeared with a vengeance to enable designers to rapidly prototype
new OLTP systems and thus bring them to market faster. Less confident generalists could even
design databases and manipulate them thanks to these tools which abstracted away the details
to just get the job done. The tools made engineers and non-engineers productive in building
database driven applications rapidly. Unfortunately, there barely are any good browsers for
LDAP much less topology/schema, design and tuning tools. The barren tooling landscape leaves
developers and data architects exposed enough to turn back to the RDBMS for immediate comfort.
This temporary gain is at the cost of long term data bottle necks or synchronization issues.</p>
+<p>Regardless of which factor prevents most the uptake of LDAP, the fact remains: the
wrong decisions are being made more often than the right ones. It's a matter of time before
Directories are considered antiquated technologies unless they can accommodate modern needs.
Directories must be compelling enough for data architects and developers to decide to utilize
them for their strengths in theory and in practice.</p>
+<h2 id="renovating-ldap-directories-for-the-21st-century">Renovating (LDAP) Directories
for the 21st Century</h2>
+<p>Several factors are not under the immediate control of the LDAP community however
enough are to bring LDAP to the 21st century. First and foremost, LDAP tooling must improve.
We need tools to model LDAP directories properly for topology and schema. Designers should
be guided on how they can properly use more of the esoteric constructs to control the naming,
and hierarchy of the directory. There's more to directory design than just objectClasses and
attributeTypes.</p>
+<p>Secondly the protocol must expand LDAP to include standard mechanisms for declaring
triggers, stored procedures and views. These two aspects alone contribute to the vast majority
of reasons why relational databases store information best accessed from a directory. Allowing
these new constructs for a directory will enable virtualization, provisioning, referential
integrity, and server interaction with the external environment. Rather than only exposing
access to static information (white pages) the directory could be utilized to solve many more
problems confronting designers and developers in today's integration era. The Directory would
truly become the Swiss Army Knife(TM) of integration tools in the data architect's tool chest.</p>
+<h2 id="conclusion-the-aim-of-the-apache-directory-project">Conclusion: The Aim of
the Apache Directory Project</h2>
+<p>At the Apache Directory Project, there are two LDAP specific projects. The first
is a pure Java LDAP Server called Apache Directory Server (ApacheDS) which has been written
and certified by the Open Group for LDAPv3. It was started in reaction to the often brittle
code that was too hard to manage: the code was written in C and had preprocessor directives
strewn all over it for porting.</p>
+<p>The other LDAP related project is called Apache Directory Studio. It is intended
to provide the missing LDAP tooling support in addition to Apache Directory Server specific
management utilities.</p>
+<p>The general motives for forming the Apache Directory Project can be summarized with
the points below:</p>
+<ul>
+<li>Avoid low level compiled language for:</li>
+<li>Reducing complexity, and increase productivity</li>
+<li>Enabling portability to other platforms with minimal effort</li>
+<li>Attracting more contributors with most common language (Java)</li>
+<li>Devise a more flexible dynamic server designed for:<ul>
+<li>Extension</li>
+<li>Protocol experimentation</li>
+<li>Hot plug-ability</li>
+<li>Simplicity</li>
+</ul>
+</li>
+<li>Experiment with and introduce new integration tier constructs for directories:<ul>
+<li>Triggers</li>
+<li>Views</li>
+<li>Stored Procedures</li>
+<li>Queues</li>
+</ul>
+</li>
+<li>Provide the missing tooling critical for:<ul>
+<li>LDAP Adoption (general for all LDAP servers)</li>
+<li>Increasing user comfort with LDAP</li>
+<li>Lessening the learning curve for those using LDAP</li>
+</ul>
+</li>
+<li>Stimulate commercial vendors to adopt these new capabilities to remain competitive.</li>
+</ul>
+<p>One of our aims is to induce thought in the LDAP community while stimulating its
growth through simple useful products. The more satisfied LDAP users are, the bigger the community
using and interested in LDAP. This is where simple intuitive tooling and a server come in
hand. More than that, these projects serve as an experimentation platform for devising new
constructs in the protocol and evaluating their utility without breaking with the existing
protocol. This is why certification is very important to us as we devise new constructs to
make LDAP much more useful to its users.</p>
+<p>Ultimately we want to see changes appearing in the protocol standard which make
LDAP a more familiar hence appealing, and easier to use technology. With standards around
these new constructs interoperability could be achieved. Users will not be bound to a specific
server. We want to demonstrate the viability and profound effects of these new constructs
in the protocol through our example while stimulating commercial vendors to do the same to
remain competitive. It does not matter to us which LDAP server is used so long as the users'
situation improves with these new productive protocol features to make LDAP serve its intended
purpose and go beyond. We strive, in this way, to increase LDAP awareness, comfort and adoption
to bring forth what we call the Modern LDAP Renaissance.</p>
+
+
+
+                </div><!-- rightColumn -->
+                <div id="endContent"></div>
+            </div><!-- content -->
+            <div id="footer">&copy; 2003-2012, <a href="http://www.apache.org">The
Apache Software Foundation</a> - <a href="privacy-policy.html">Privacy Policy</a><br
/>
+                Apache Directory, ApacheDS, Apache Directory Server, Apache Directory Studio,
Apache LDAP API, Apache Triplesec, Triplesec, Apache, the Apache feather logo, and the Apache
Directory project logos are trademarks of The Apache Software Foundation.
+            </div>
+        </div><!-- container -->
+    </body>
+</html>
\ No newline at end of file



Mime
View raw message