Yes, in fact, what I'm trying to do is serialize the stream of operations that occur during the rewind cycle, without actually re-doing the render. This is a much more natural approach I think. Certainly, everything that works today will work in the future, but a lot of things become more simple and effecient. That is, there's an efficiency of scale in having a single hidden form field with all the serialized/compressed/MIME-encoded data than having lots of such hidden fields, the way we do today.
What I want is to ensure we can continue to create complex forms with loops and conditionals and have them continue to work. On 1/9/06, Patrick Casey <[EMAIL PROTECTED]> wrote: > > Wouldn't Howard's proposed approach of serializing and compressing > all relevant page data in the outbound stream and then echoing it back in > the POST still let you do things like loops, but without having to muck > around with the rewind cycle? I don't see why his approach would prevent you > doing what you want to do, while it would definitely save a great deal of > the headache associated with the rewind cycle. It is, after all, the way > .net has been doing it for 3 or so years and it seems to work for them. > > --- pat > > > > -----Original Message----- > > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Nathan Kopp > > Sent: Monday, January 09, 2006 8:39 PM > > To: tapestry-user@jakarta.apache.org > > Subject: Why I like the rewind cycle > > > > I've written a blog post on why I like Tapestry's poorly-named-yet-very- > > useful > > "rewind cycle." Before we get out the torches and pitchforks and > > eradicate all > > memories of the dreaded rewind cycle from Tapestry's code, let's have a > > look at > > what it has to offer and maybe think about why it was created in the first > > place. :-) That way we won't lose functionality when the replacement is > > designed and built. > > > > Here's the blog post: > > http://nate-tech.blogspot.com/2006/01/why-tapestrys-crazy-rewind-is- > > good.html > > > > To summarize (for those who's time is limited), I like how the rewind > > cycle > > replays the page render for processing, because (among other things) it > > allows > > components to be bound directly to loop variables, so I don't need to > > track a > > loop index for my bindings. No other framework that I know of can do this > > in > > such an elegant way as Tapestry. > > > > BTW, I have really enjoyed working with Tapestry, especially Tap 4. This > > is > > great stuff! > > > > -Nathan Kopp > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
