Eelco Hillenius wrote:
Actually, when you look closer to the whole continuation thing, continuations are not so incompattible with how Wicket works now.
I guess the problem is that continuations are not really compatible with java. An elegant implementation of continuations in java seems to be impossible.
The
original idea of continuations is to never return a value, but pass a context object (continuation) to the next function call. That idea translated to webapplications seems to be to have a 'wait-for-input' concept, so that you can model a flow like a couple of linear steps that conceptually 'pause'/ wait for input before it moves to the next step. As Wicket has a current state and does not work with return values for flow, I think we could defend that we do the same thing as the original definition, though with a slightly different flavor. At least it has the same net effect. And... if you want to do the web variant of continuations... that's easy... just create a mini framework that handles the flow and - I think - you're done.
That would just be a state machine.
Or... maybe I don't get the idea of continuations just yet. Please correct me if that is the case :)
Have a look at this article: http://www-128.ibm.com/developerworks/library/j-contin.html
Jetty 6 is going to have continuation support. Are there any plans of supporting jetty continuations?
http://www.mortbay.com/MB/log/gregw/?permalink=Jetty6Continuations.html Timo ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
