[Gzz-commits] storm/doc/pegboard/storm_with_tapestry--hemppah...

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/storm
Module name:    storm
Branch:         
Changes by:     Hermanni Hyytiälä <address@hidden>      03/07/08 04:24:39

Modified files:
        doc/pegboard/storm_with_tapestry--hemppah: peg.rst 

Log message:
        more twids

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst.diff?tr1=1.16&tr2=1.17&r1=text&r2=text

Patches:
Index: storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst
diff -u storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst:1.16 
storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst:1.17
--- storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst:1.16        Tue Jul 
 8 03:28:01 2003
+++ storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst     Tue Jul  8 
04:24:38 2003
@@ -5,8 +5,8 @@
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-07-03
-:Last-Modified: $Date: 2003/07/08 07:28:01 $
-:Revision: $Revision: 1.16 $
+:Last-Modified: $Date: 2003/07/08 08:24:38 $
+:Revision: $Revision: 1.17 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -39,24 +39,24 @@
 Introduction to Tapestry
 ========================
 
-Tapestry_ is a application level Peer-to-Peer overlay. Currently Tapestry_ 
-supports the DOLR abstracion but other abstraction can be implemented 
-(e.g., DHT). Tapestry's DOLR interface has two primary functions: efficient 
-way for nodes to communicate across the overlay and effcient object location. 
+Tapestry_ is an application level Peer-to-Peer overlay. Currently Tapestry 
+supports the `DOLR abstraction`_ but other abstraction can be implemented 
+(e.g., DHT_). Tapestry's DOLR interface has two primary functions: efficient 
+point to point message delivery and effcient object location. 
 In Tapestry, objects are *published* with object to location mappings (a.k.a. 
-pointers). This operation differs from DHTs in that always use the closest 
-available object.
+pointers). This operation differs from DHTs in that Tapestry always tries use 
+the closest available object.
 
 Tapestry's routing table consists of levels of neighbor links. Each level 
-represents a matching prefix up to a digit position in the ID. Additionally
+represents a matching prefix up to a digit position in the ID. Additionally,
 for each level, neighbor links are selected based on closest in network 
 *latency*. Along the publication process, the overlay deposits a pointer at 
 every hop along the way. When an object is searched, a query is forwarded 
 towards object's publication route, and when a query run into a first pointer, 
 overlay directly forwards to the object.
 
-Tapestry 2.0 release is written in Java and uses SEDA (Staged Event-Driven 
-Architecture) framwork for thread and I/O-operations. Tapestry's code base
+Tapestry 2.0 release is written in Java and uses SEDA_ (Staged Event-Driven 
+Architecture) framework for thread and I/O-operations. Tapestry's code base
 has approximately 57000 lines of code and shares some code with Oceanstore's
 code base.
 
@@ -64,18 +64,18 @@
 ================
 
 SEDA_ is an asynchronous I/O library (similar to JDK 1.4's java.nio package). 
In
-SEDA there are stages and they communicate with each other by sending events.
-A stage runs as a thread which starts by executing initialization routines and 
+the SEDA model, there are stages and they communicate with each other by 
sending 
+events. A stage runs as a thread which starts by executing initialization 
routines and 
 then enters an event loop.  Inside each JVM, a dispatcher monitors all 
messages 
 and events, and delivers copies to each stage that subscribes to messages of 
 that type.
 
-Each Tapestry component is implemented as a stage. A (common) Tapestry node 
-uses StaticTClient stage, DynamicTClient stage, Router stage and Tapestry 
-application stage. For each stage, a config file is required to specify 
-stage's properties (XML-like tag structure). During the initialization phase, 
-a stage specifies which event and messages it wants to "listen" to. For Storm, 
-the Tapestry application stage is the most important. 
+Currently, each Tapestry component is implemented as a stage. For example, 
+A (common) Tapestry node uses StaticTClient stage, DynamicTClient stage, 
Router 
+stage and Tapestry application stage. For each stage, a config file is 
required 
+to specify stage's properties (XML-like tag structure). During the 
initialization 
+phase, a stage specifies which event and messages it wants to "listen" to. For 
+Storm, the Tapestry application stage is the most important. 
 
 
 Overview of Tapestry API
@@ -100,7 +100,7 @@
    
 
 However, the implemented API, according to the JavaDocs, offers services with 
-the following names (and some other functionality):
+the following names (and some additional services):
 
     TapestryRouteMsg(SecureHash peer) - analog to RouteToObject(O_GUID)
     
@@ -128,8 +128,8 @@
 Using Tapestry API from other applications
 ==========================================
 
-According to the `Tapestry programmer's guide`_, there three steps to write
-a Tapestry application:
+According to the `Tapestry programmer's guide`_, there are three steps to write
+an application that uses Tapestry's services:
 
    - Write the necessary messages to interface with Tapestry
    - Write an event handler class that would serve as the application
@@ -143,7 +143,7 @@
 
 1. An application must extend extending the abstract API message types, e.g.:
 
-   public class StormMsg extends TapestryPublishmsg {
+   public class StormLocateMsg extends TapestryLocateMsg {
 
 2. Class must have own serialization methods in order transfer messages over a 
 network:
@@ -157,7 +157,7 @@
 An event handler class
 ------------------
 
-1. Write a eventhandler class which extends SEDA's existing stages, e.g.,
+1. Write an eventhandler class which extends SEDA's existing stages, e.g.,
 
   public class StormTapestryManager implements EventHandlerIF
   
@@ -410,3 +410,5 @@
 .. _Tapestry: 
http://www.cs.berkeley.edu/~ravenben/publications/pdf/tapestry_jsac.pdf
 .. _`Tapestry website`: http://www.cs.berkeley.edu/~ravenben/tapestry/
 .. _SEDA: http://www.eecs.harvard.edu/~mdw/proj/seda
+.. _`DOLR abstraction`: 
http://www.cs.berkeley.edu/~ravenben/publications/pdf/apis.pdf
+.. _DHT: http://www.cs.berkeley.edu/~ravenben/publications/pdf/apis.pdf