[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/28 07:51:33

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.28&tr2=1.29&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.28 
storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst:1.29
--- storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst:1.28        Tue Jul 
22 03:28:42 2003
+++ storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst     Mon Jul 28 
07:51:33 2003
@@ -5,8 +5,8 @@
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-07-03
-:Last-Modified: $Date: 2003/07/22 07:28:42 $
-:Revision: $Revision: 1.28 $
+:Last-Modified: $Date: 2003/07/28 11:51:33 $
+:Revision: $Revision: 1.29 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -62,7 +62,8 @@
        The first three classes are used with HTTP-Kit and the three 
        latter ones with GISP. Obviously, GISP related classes are not a problem
        as they are obsolete but HTTP-Kit related may be a problem, i.e., 
classes 
-       have to re-engineer to SEDA compliant classes.
+       have to re-engineer to SEDA compliant classes. UPDATE: This is not
+       necessary; see the next ISSUE.  
        
 ISSUE: If a software uses SEDA in one component, is it mandatory to use SEDA's
        thread-event model in all other components also (i.e. native Java 
threads