No real thoughts on this so far. With super-super effort, it might be possible to do continuations that way Cocoon and RIFE does them, but I'm not convinced that's the right approach. There's a limit to how much magic even I want to put into the bytecode. What I'm trying to do is set things up such that work is funneled through a couple of hookable pipelines with enough information and context to allow a state-flow mechanism to arbitrate operations. We'll have to see how it evolves. Basics first.
On 10/21/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
It's possible, but I'm not sure if he has looked at them. (though don't let me put words in his mouth because I obviously don't know how he thinks ;) ) Perhaps you could start a wiki page outlining how/why you think they might be useful in Tapestry? (I must confess to only having a rudimentary understanding of them. ) Are they related to cometd style IO at all? I think they must be somehow. I personally ~am~ very excited about adding support for that in. On 10/21/06, Bill Holloway <[EMAIL PROTECTED]> wrote: > > Will Tapestry 5 support continuations built-in? Or will I need to > stay with Spring WebFlow? > > bill > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
