directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r124959 - in incubator/directory: naming/trunk server/trunk sitedocs/trunk/xdocs sitedocs/trunk/xdocs/images
Date Wed, 12 Jan 2005 09:30:30 GMT
Author: akarasulu
Date: Wed Jan 12 01:30:27 2005
New Revision: 124959

Changes ...

 o added image map to the front page of sitedocs
 o added support in server and naming for dist:multiproject
 o with patch below the dist plugin will do all javadoc 
   consolidation as well as include what ever is needed 
   for both bimary and source distros:

   incubator/directory/sitedocs/trunk/xdocs/images/50k-ft-architecture.png   (contents, props
   incubator/directory/naming/trunk/   (props changed)

Modified: incubator/directory/naming/trunk/maven.xml
--- incubator/directory/naming/trunk/maven.xml	(original)
+++ incubator/directory/naming/trunk/maven.xml	Wed Jan 12 01:30:27 2005
@@ -44,7 +44,10 @@
           todir="${basedir}/naming-config/xdocs" overwrite="true"/>
-  <!-- Generate combined javadoc -->
+  <!-- No longer need since consolidated doc generation is
+       now present within the dist plugin using the dist:multiproject
+       goal
   <postGoal name="multiproject:site">
     <javadoc destdir="${}/apidocs">
       <packageset dir="${basedir}/naming-core/src/java"/>
@@ -60,6 +63,7 @@
+  -->
   <!-- Delete temp copies of naming-core navigation.xml -->
   <postGoal name="multiproject:site">

Modified: incubator/directory/naming/trunk/
--- incubator/directory/naming/trunk/	(original)
+++ incubator/directory/naming/trunk/	Wed Jan 12 01:30:27 2005
@@ -27,3 +27,4 @@

Deleted: /incubator/directory/server/trunk/maven.xml

Modified: incubator/directory/server/trunk/
--- incubator/directory/server/trunk/	(original)
+++ incubator/directory/server/trunk/	Wed Jan 12 01:30:27 2005
@@ -28,3 +28,4 @@

Added: incubator/directory/sitedocs/trunk/xdocs/images/50k-ft-architecture.png
Binary file. No diff available.

Modified: incubator/directory/sitedocs/trunk/xdocs/index.xml
--- incubator/directory/sitedocs/trunk/xdocs/index.xml	(original)
+++ incubator/directory/sitedocs/trunk/xdocs/index.xml	Wed Jan 12 01:30:27 2005
@@ -8,17 +8,50 @@
     <section name="What is it?">
-        The Directory Project is an attempt to centralize all naming and 
-        directory needs in one place at the ASF.  This incubator project is
-        language independent however its primary goal to graduate the incubator
-        is to provide a pure Java LDAP directory server called Eve.  Other 
-        projects have come to be to factor out useful code from the server and
-        some have just found their final home.  These subprojects are described
-        in the section below and to a greater detail within their own 
-        documentation.
+        Before going into all the details here's what the Apache Directory
+        server looks like?  Feel free to navigate the image map to the various
+        components of the server.  This will naturally lead to several 
+        questions which will hopefully be answered further below.
-    </section>
+      <map name="server">
+  <area shape="rect" alt="Network Frameworks" href=""
target="" title="Network Frameworks"
coords="39,155,603,201" />
+  <area shape="rect" alt="Apache Directory Server Core" href=""
title="Apache Directory Server Core" coords="209,277,612,443" />
+  <area shape="rect" alt="Kerberos Provider" href=""
target="" title="Kerberos
Provider" coords="457,210,530,225" />
+  <area shape="rect" alt="LDAP Provider" href=""
target="" title="LDAP Provider"
+  <area shape="rect" alt="DNS Provider" href=""
target="" title="DNS Provider"
coords="209,210,283,224" />
+  <area shape="rect" alt="DHCP Provider" href=""
target="" title="DHCP Provider"
coords="128,210,202,225" />
+  <area shape="rect" alt="NTP Provider" href=""
target="" title="NTP Provider"
coords="44,209,118,224" />
+<img usemap="server" src="./images/50k-ft-architecture.png"/>
+      <p>
+        Our primary vision (others also outlined below) is to build an 
+        enterprise directory server platform (and its components) where 
+        other Internet services snap in to store their data within the 
+        directory so they may be managed using LDAP.  From the image 
+        above you'll see the architecture is designed so services besides
+        LDAP like DNS, DHCP, SLP and Kerberos will snap in.  Other services
+        like UDDI can also be implemented and snapped in.  These services 
+        will use a common networking layer and each can be toggled on and
+        off according to the needs of the environment.  apseda, mina, or 
+        sedang are various frameworks used for the common network layer. 
+        These services share the common network layer and back their data 
+        within the Apache Directory Server's backing stores without any 
+        network latency or going through the LDAP line protocol.  NTP btw
+        is the only exception and it's there to remedy the need for time 
+        sync for replication and other time sensitive protocols like kerberos.
+        Its implementation here is intended to prevent any dependency on
+        external infrastructure.
+      </p>
+      <p>
+        Other aspects to our vision include becoming the JNDI goto project and 
+        also becoming the one stop shop for all directory and naming concerns 
+        here at the ASF.  These concerns may be outside of the scope of JNDI 
+        or may not even fall under Java.
+      </p>
+    </section>
     <section name="Incubation Disclaimer">
         The Directory Project is an effort undergoing incubation at the Apache 
@@ -33,90 +66,8 @@
         The status of the Directory Project is tracked by the Apache Incubator
-        <a href="">here</a>.
-      </p>
-    </section>
-    <!-- This section duplicates subprojects/index.xml. 
-    Not sure we should allow this kind of duplication. I fear we might end up with broken
-    <section name="Subprojects">
-      <table>
-        <tr><th>Subproject</th><th>Description</th></tr>
-        <tr>
-          <td><a href="subprojects/eve/index.html">Eve</a></td>
-          <td>
-            Eve is a modular LDAP server written in pure Java.  The Eve server
-            is being completely designed from the ground up here within the 
-            incubator and will gain from the experience of building the old 
-            LDAPd server.
-          </td>
-        </tr>
-        <tr>
-          <td><a href="subprojects/directory-ldap/index.html">LDAP</a></td>
-          <td>
-            Commons code dealing with the Lightweight Directory Access Protocol
-            is managed under this subproject.  This will include a common API 
-            for composing and reading LDAP Message envelopes and various LDAP 
-            clients including JNDI LDAP providers.
-          </td>
-        </tr>
-        <tr>
-          <td><a href="subprojects/janus/index.html">Janus</a></td>
-          <td>
-            Janus is a <a href="">AAA
-            </a> framework and possibly in the future a AAA protocol 
-            implementation.  According to the <a href="">IETF</a>
-            the Authentication, Authorization and Accounting working group was 
-            formed to specify a general Authentication, Authorization, and 
-            Accounting protocol for the Internet.  Janus is an implementation of
-            that specification.
-          </td>
-        </tr>
-        <tr>
-          <td><a href="subprojects/directory-naming/index.html">Naming</a></td>
-          <td>
-            There is a set of core functionality common to all JNDI providers 
-            and JNDI does not necessarily revolve around LDAP and X.500 
-            directories.  The naming subproject will contain common JNDI code 
-            along with various JNDI provider's.  A J2EE ENC, environment naming 
-            context would be one implementation.  If you're looking to build a 
-            JNDI provider you might want to take a look in here before 
-            proceeding.
-          </td>
-        </tr>
-        <tr>
-          <td><a href="subprojects/snickers/index.html">Snickers</a></td>
-          <td>
-            Both LDAP and X.500 directories have their data structures defined 
-            using the Abstract Syntax Notation One language.  The entire X.500 
-            ITU series of specifications use ASN.1 to define the data structures
-            that are transmitted over the wire using various encodings (like 
-            BER, DER, PER, and XER).   ASN.1 is used as a Protocol Data Unit 
-            definition syntax in several other protocols like SNMP.  Snickers 
-            will contain code factored out of the Eve and LDAP subprojects used
-            to encode and decode ASN.1 messages.  Snickers will eventually grow
-            to contain various language stub generators (ASN.1 compilers) that
-            create stub structures, classes and interfaces for ASN.1 
-            definitions.  Snickers, in this way, is a SNACC and SNACC4J 
-            replacement for C/C++ and Java respectively.
-          </td>
-        </tr>
-        <tr>
-          <td><a href="subprojects/sitedocs/index.html">Sitedocs</a></td>
-          <td>
-            The structure and organization of the entire website and how to 
-            manage it is discribed here.
-          </td>
-        </tr>
-      </table>
+        <a href="">here</a>.
+      </p>
-    -->

View raw message