directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From akaras...@apache.org
Subject svn commit: rev 6650 - incubator/directory/eve/trunk/eve/xdocs/frontend
Date Sat, 14 Feb 2004 07:00:11 GMT
Author: akarasulu
Date: Fri Feb 13 23:00:10 2004
New Revision: 6650

Added:
   incubator/directory/eve/trunk/eve/xdocs/frontend/misc.xml
Modified:
   incubator/directory/eve/trunk/eve/xdocs/frontend/events.xml
   incubator/directory/eve/trunk/eve/xdocs/frontend/navigation.xml
   incubator/directory/eve/trunk/eve/xdocs/frontend/performance.xml
   incubator/directory/eve/trunk/eve/xdocs/frontend/pushing-jndi.xml
   incubator/directory/eve/trunk/eve/xdocs/frontend/requirements.xml
   incubator/directory/eve/trunk/eve/xdocs/frontend/resource-pooling.xml
   incubator/directory/eve/trunk/eve/xdocs/frontend/seda.xml
Log:
added a little bit of stuff

Modified: incubator/directory/eve/trunk/eve/xdocs/frontend/events.xml
==============================================================================
--- incubator/directory/eve/trunk/eve/xdocs/frontend/events.xml	(original)
+++ incubator/directory/eve/trunk/eve/xdocs/frontend/events.xml	Fri Feb 13 23:00:10 2004
@@ -2,7 +2,7 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: Event Decoupling</title>
+    <title>Event Decoupling</title>
   </properties> 
   
   <body>

Added: incubator/directory/eve/trunk/eve/xdocs/frontend/misc.xml
==============================================================================
--- (empty file)
+++ incubator/directory/eve/trunk/eve/xdocs/frontend/misc.xml	Fri Feb 13 23:00:10 2004
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<document>
+  <properties>
+    <author email="akarasulu@apache.org">Alex Karasulu</author>
+    <title>SEDA Approach</title>
+  </properties> 
+  
+  <body>
+    <section name="Design for blocking IO too?">
+      <p>
+        All aspects of the server will be based on non-blocking IO constructs.
+        There simply is no point to writing a stateful protocol server any 
+        other way.  The code of the server could be designed to support any
+        implementation whether it based on blocking IO or not.
+      </p>
+      
+      <p>
+        The frontend from the ground up is designed to use non-blocking IO and
+        it makes even less sense to consider anything else when the SEDA based 
+        approach is also considered.
+      </p>
+      
+      <p>
+        A primary requirement on the server is to remain pure Java compliant.
+        That means we're left with whatever the JDK gives us in terms of 
+        non-blocking mechanisms.  We are pretty sure that Selectors and Channels
+        are the construct from now until a very long time.  Now this may change
+        and adaptation may be required but its a ways out if at all.
+      </p>
+      
+      <p>
+        There is no point to us writing generic code to accomodate blocking IO.
+        It should not really matter to us if some of the details of the 
+        standard non-blocking constructs of the JDK leak out reveiling a 
+        non-blocking implementation.  Who cares?  Why was the time bothering 
+        with the old way of doing things?
+      </p>
+      
+      <p>
+        We try not expose our non-blocking implementation details but they 
+        have leaked out in minor areas.   Monitors for the input and listener
+        modules show methods taking Selectors and their keys.  This is ok with
+        us for now because well the monitor needs deal with failures in the
+        selection process.  They are not core functional components and can be
+        changed over time.  Nothing critical like a component's service 
+        interface exposes these NIO classes.
+      </p>
+    </section>
+  </body>
+</document>

Modified: incubator/directory/eve/trunk/eve/xdocs/frontend/navigation.xml
==============================================================================
--- incubator/directory/eve/trunk/eve/xdocs/frontend/navigation.xml	(original)
+++ incubator/directory/eve/trunk/eve/xdocs/frontend/navigation.xml	Fri Feb 13 23:00:10 2004
@@ -38,6 +38,7 @@
             <item name="Resource Pooling" href="/frontend/resource-pooling.html"/>
             <item name="Pushing the JNDI" href="/frontend/pushing-jndi.html"/>
             <item name="Components" href="/frontend/components/index.html"/>
+            <item name="Miscellaneous" href="/frontend/components/misc.html"/>
             <item name="Current Status" href="/frontend/status.html"/>
           </item>
         </item>

Modified: incubator/directory/eve/trunk/eve/xdocs/frontend/performance.xml
==============================================================================
--- incubator/directory/eve/trunk/eve/xdocs/frontend/performance.xml	(original)
+++ incubator/directory/eve/trunk/eve/xdocs/frontend/performance.xml	Fri Feb 13 23:00:10 2004
@@ -2,12 +2,14 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: High Performance IO</title>
+    <title>High Performance IO</title>
   </properties> 
   
   <body>
     <section name="High Performance IO">
-      <p>Coming soon ...</p>
+      <p>
+        
+      </p>
 
       <!--
       <subsection name="">

Modified: incubator/directory/eve/trunk/eve/xdocs/frontend/pushing-jndi.xml
==============================================================================
--- incubator/directory/eve/trunk/eve/xdocs/frontend/pushing-jndi.xml	(original)
+++ incubator/directory/eve/trunk/eve/xdocs/frontend/pushing-jndi.xml	Fri Feb 13 23:00:10
2004
@@ -2,7 +2,7 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: Pushing JNDI</title>
+    <title>Pushing JNDI</title>
   </properties> 
   
   <body>

Modified: incubator/directory/eve/trunk/eve/xdocs/frontend/requirements.xml
==============================================================================
--- incubator/directory/eve/trunk/eve/xdocs/frontend/requirements.xml	(original)
+++ incubator/directory/eve/trunk/eve/xdocs/frontend/requirements.xml	Fri Feb 13 23:00:10
2004
@@ -2,7 +2,7 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: Requirements</title>
+    <title>Requirements</title>
   </properties> 
   
   <body>

Modified: incubator/directory/eve/trunk/eve/xdocs/frontend/resource-pooling.xml
==============================================================================
--- incubator/directory/eve/trunk/eve/xdocs/frontend/resource-pooling.xml	(original)
+++ incubator/directory/eve/trunk/eve/xdocs/frontend/resource-pooling.xml	Fri Feb 13 23:00:10
2004
@@ -2,7 +2,7 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: Resource Pooling and Sharing</title>
+    <title>Resource Pooling and Sharing</title>
   </properties> 
   
   <body>

Modified: incubator/directory/eve/trunk/eve/xdocs/frontend/seda.xml
==============================================================================
--- incubator/directory/eve/trunk/eve/xdocs/frontend/seda.xml	(original)
+++ incubator/directory/eve/trunk/eve/xdocs/frontend/seda.xml	Fri Feb 13 23:00:10 2004
@@ -2,12 +2,33 @@
 <document>
   <properties>
     <author email="akarasulu@apache.org">Alex Karasulu</author>
-    <title>Apache Directory Project: SEDA Approach</title>
+    <title>SEDA Approach</title>
   </properties> 
   
   <body>
     <section name="SEDA Approach">
-      <p>Coming soon ...</p>
+      <p>
+        At the present moment, the performance benefits of SEDA are at the
+        top of the list.  Other features which make SEDA based servers more
+        instrumentable, resilient and extensible are not sought after at the
+        present moment.  Under heavy load we would like the server to perform 
+        well without rapid degradation while servicing requests.
+      </p>
+      
+      <p>
+        Furthermore we want to add these features without incurring more 
+        complexity in the server's design.  Keeping things as simple as possible
+        is a driving factor in our approach simple SEDA implementation.  Hence
+        to simple SEDA stage is simply a combination of a event queue, thread 
+        pool, stage handler, and a driver thread.  The one extra feature we do
+        support is the EnquePredicates which might be used to manage load 
+        shedding.
+      </p>
+      
+      <p>
+        The simple SEDA code can be found the common frontend API within the
+        <a href="">org.apache.eve.seda</a> package.
+      </p>
     </section>
   </body>
 </document>

Mime
View raw message