[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/14 02:44:28

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

Log message:
        huh - thread issue solved :)

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst.diff?tr1=1.23&tr2=1.24&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.23 
storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst:1.24
--- storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst:1.23        Thu Jul 
10 05:07:55 2003
+++ storm/doc/pegboard/storm_with_tapestry--hemppah/peg.rst     Mon Jul 14 
02:44:28 2003
@@ -5,8 +5,8 @@
 
 :Authors:  Hermanni Hyytiälä
 :Date-Created: 2003-07-03
-:Last-Modified: $Date: 2003/07/10 09:07:55 $
-:Revision: $Revision: 1.23 $
+:Last-Modified: $Date: 2003/07/14 06:44:28 $
+:Revision: $Revision: 1.24 $
 :Status:   Incomplete
 
 .. :Stakeholders:
@@ -68,24 +68,14 @@
        thread-event model in all other components also (i.e. native Java 
threads
        are not allowed)?
        
-.. I realized this "Don't allocate or manage threads in your application" 
-   (possible) issue while I was reading Sandstorm Tutorial and 
-   User's Guide. This "feature" of SEDA has not been mentioned anywhere in 
Tapestry
-   website, nor Tapestry installation guide, nor Tapestry Programmer's guide,
-   nor Javadocs!
-   
-   If a software cannot use native Java threads as one software
-   component uses SEDA's thread-event model, it's a *major* issue for us. Thus,
-   the choices are:
-   
-   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...
-   
-   
-              
+SOLVED: According to Matt Welsh, the author of SEDA/Sandstorm framework, we are
+        able to use native (Java) threads while using SEDA in a software:
+       
+           It is true that SEDA intends to manage all of the threads in the 
system
+           itself. However, it should be fine to use your own threads as long 
as
+            you yield or sleep often enough for SEDA's threads to get a chance 
to
+            run. Let me know how it goes!
+       
 
 Introduction to Tapestry
 ========================