[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/10 05:07:55

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

Log message:
        one more option

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst.diff?tr1=1.22&tr2=1.23&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.22 
storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst:1.23
--- storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst:1.22        Thu Jul 
10 02:38:49 2003
+++ storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst     Thu Jul 10 
05:07:55 2003
@@ -5,8 +5,8 @@
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-07-03
-:Last-Modified: $Date: 2003/07/10 06:38:49 $
-:Revision: $Revision: 1.22 $
+:Last-Modified: $Date: 2003/07/10 09:07:55 $
+:Revision: $Revision: 1.23 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -78,8 +78,9 @@
    component uses SEDA's thread-event model, it's a *major* issue for us. Thus,
    the choices are:
    
-   1) Dumb Tapestry (the better choice)
+   1) Dumb Tapestry (the best choice?)
    2) Re-engineer Fenfire framework to SEDA compliant (a very bad choice)
+   3) Implement a Seda-free Tapestry (possible, but may required lot of work)
    
    I will investigate this more carefully...