Actually, instead of just looking at the name, continuations, you should look at want you want to acchieve. And then the large thing with continuations would be that you could do:
... init components ... ... render page ... ... getUserInput and do something with it ... ... processAndWait ... ... getUserInput and do something with it ... ... end program ... That's kind of the continuations idea. It works for workflow driven applications or wizard style (sub)applications. If you want, you can implement this style of coding in Wicket. I see no reasons why you couldn't. If Geert Bevin (the RIFE guy) is succesful in abstracting a generic (web) continuations framework, we would be happy to support it with Wicket. There actually has been some talk about it here and there, and we (Geert and I) hope to have a chat next month at JavaPolis (which maybe gives me more insight at the continuations thing ;)). He seems to be a nice guy interested in working together with other people/ frameworks; in fact I think the guys of WebWork and he are working together on abstracting the continuations concept too (again, hat's off for the WebWork guys that are doing a lot of behind-the-scenes contributing to different frameworks, including Wicket). Until then, we are not planning any special support for continuations in Wicket - of course you are free to suggest contributions - and I'd be more interested to see what you'd like to acchieve instead of just hearing about the hype factor. Eelco ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
