You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by er...@apache.org on 2006/01/26 23:32:32 UTC
svn commit: r372635 [3/6] - in /directory/trunks/apacheds/site: ./ src/
src/site/ src/site/resources/ src/site/resources/developers/
src/site/resources/images/ src/site/resources/users/ src/site/xdoc/
src/site/xdoc/developers/ src/site/xdoc/drafts/ src...
Added: directory/trunks/apacheds/site/src/site/xdoc/developers/networking.xml
URL: http://svn.apache.org/viewcvs/directory/trunks/apacheds/site/src/site/xdoc/developers/networking.xml?rev=372635&view=auto
==============================================================================
--- directory/trunks/apacheds/site/src/site/xdoc/developers/networking.xml (added)
+++ directory/trunks/apacheds/site/src/site/xdoc/developers/networking.xml Thu Jan 26 14:29:42 2006
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="akarasulu@apache.org">Alex Karasulu</author>
+
+ </properties>
+
+ <body>
+ <section name="Networking">
+ <p>
+ We wanted to keep the networking code as independent as possible to
+ prevent it's concerns from creeping into the LDAP protocol handling
+ code. Furthermore we wanted it to be independent of the LDAP protocol
+ so it can be reused as much as possible with other protocols.
+ </p>
+
+ <p>
+ This lead to the creation of a newtorking framework or two. These
+ frameworks use different approaches and models to provide the network
+ plumbing needed by internet protocol servers. A common protocol
+ provider API is used to implement protocols enabling the provider on
+ all network frameworks.
+ </p>
+
+ <p>
+ Each network framework at the directory project has its own project so
+ its best to delegate a description of each framework to the appropriate
+ project documentation:
+ </p>
+
+ <table>
+ <tr>
+ <th>Framework</th> <th>Description</th>
+ </tr>
+
+ <tr>
+ <td><a href="../../seda/index.html">seda</a></td>
+
+ <td>
+ A simple framework for implementing staged event driven internet
+ protocol servers.
+ </td>
+ </tr>
+
+ <tr>
+ <td><a href="../../seda/index.html">sedang</a></td>
+
+ <td>
+ The next generation seda framework based on d-haven event packages.
+ </td>
+ </tr>
+
+ <tr>
+ <td><a href="../../mina/index.html">mina</a></td>
+
+ <td>
+ Multipurpose Infrastrusture for Network Applications based on ACE.
+ </td>
+ </tr>
+ </table>
+ </section>
+
+ </body>
+</document>
Added: directory/trunks/apacheds/site/src/site/xdoc/developers/partitions.xml
URL: http://svn.apache.org/viewcvs/directory/trunks/apacheds/site/src/site/xdoc/developers/partitions.xml?rev=372635&view=auto
==============================================================================
--- directory/trunks/apacheds/site/src/site/xdoc/developers/partitions.xml (added)
+++ directory/trunks/apacheds/site/src/site/xdoc/developers/partitions.xml Thu Jan 26 14:29:42 2006
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="akarasulu@apache.org">Alex Karasulu</author>
+
+ </properties>
+
+ <body>
+ <section name="Default Partition Design">
+ </section>
+
+ <section name="How does alias dereferencing while searching work?">
+ <p>You're going to want to read these documents here:</p>
+
+ <ul>
+ <li><a href="./xldbm.pdf">Paper LDAP database design by Tim Howes</a></li>
+ <li><a href="./alias-dereferencing.pdf">Paper on alias dereferencing mechanism by Alex Karasulu</a></li>
+ </ul>
+ </section>
+ </body>
+</document>
Added: directory/trunks/apacheds/site/src/site/xdoc/developers/protocol.xml
URL: http://svn.apache.org/viewcvs/directory/trunks/apacheds/site/src/site/xdoc/developers/protocol.xml?rev=372635&view=auto
==============================================================================
--- directory/trunks/apacheds/site/src/site/xdoc/developers/protocol.xml (added)
+++ directory/trunks/apacheds/site/src/site/xdoc/developers/protocol.xml Thu Jan 26 14:29:42 2006
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+ <properties>
+ <author email="akarasulu@apache.org">Alex Karasulu</author>
+
+ </properties>
+
+ <body>
+ <section name="Server's LDAP Protocol Provider">
+ <subsection name="Provider API">
+ <p>
+ The network layer regardless of the implementation used (seda, sedang,
+ or mina), defines protocol provider interfaces. Protocol implementors
+ only need to implement these interfaces to plug into these framework
+ implementations. A protocol provider essentially encapsulates the
+ encoding/decoding of messages and request handlers (hooks) for the
+ protocol. The networking code handles the rest to make it all work.
+ </p>
+
+ <p>
+ The directory server has one or more protocol provider
+ implementations. The primary implementation is for the LDAP protocol.
+ The provider is rather simple in nature and has some unique properties
+ which make it flexible enough to be used as an LDAP proxy server or
+ an X.500 gateway server.
+ </p>
+ </subsection>
+
+ <subsection name="Design">
+ <p>
+ The server's LDAP protocol provider translates on the wire LDAP
+ requests into JNDI LDAP operations. Results from JNDI operations are
+ then translated to LDAP responses pushed out on the wire. This thin
+ implementation makes the protocol layer efficient and easy to grasp.
+ </p>
+
+ <p>
+ The protocol provider is independent of the JNDI provider used. It is
+ however dependent on the LDAP namespace. Hence it can only work with
+ LDAP JNDI providers like the SUN LDAP JNDI provider and the server's
+ JNDI provider.
+ </p>
+
+ <p>
+ The grunt of the work done by the protocol provider is within the
+ request handlers. There is a request handler for each LDAP request
+ type.
+ </p>
+ </subsection>
+ </section>
+ </body>
+</document>
Added: directory/trunks/apacheds/site/src/site/xdoc/developers/xldbm.pdf
URL: http://svn.apache.org/viewcvs/directory/trunks/apacheds/site/src/site/xdoc/developers/xldbm.pdf?rev=372635&view=auto
==============================================================================
Binary files /tmp/tmpyYY4Ia and /tmp/tmpnq7rMj differ