I hope to abolish the rewind cycle in Tapestry 4.1.
Part of this was to deprecate the ActionLink component and action
service in 4.0 so that they could be removed in 4.1.
The outline of my approach is that there will be a single hidden form
field into which a series of objects will be serialized during the
render. These objects will control the form submission processing and
will incrementally restore server-side state during the processing.
Thus the order of operations during the render will DIRECTLY control
the order of operations during the form submission. Today, we rely on
the awkward rewind cycle, which is based on re-rendering the form and
its contents, validating against a list of form element ids.
Rather than many small hidden fields (for each For, If and Hidden,
component, as well as others) all such data will be accumulated in a
single bytestream. There is an economy of scale here ... a single
long serialized bytestream (gzipped and perhaps encrypted, then MIME
encoded) will be smaller than the sum of many individual hidden fields
(squeezed with the DataSqueezer, which often uses
serialization/gzip/MIME anyway).
I'm still struggling, however, with how to properly deal with more
dynamic ("Ajax") forms. Possibly, we'll support multiple bytestreams
handled sequentially, to cover dynamically appended forms.
On 12/20/05, Edward Scanzano <[EMAIL PROTECTED]> wrote:
> While we are the subject, will Tapestry's reliance on rewinding be revisited.
> Is there not alternative to this process. Also, we could also use more formal
> support for dynamic forms. Is this possible?
>
> Thanks
> E
>
> ----- Original Message ----
> From: Sergei Dubov <[EMAIL PROTECTED]>
> To: Tapestry users <[email protected]>
> Sent: Tuesday, December 20, 2005 13:11:11
> Subject: Re: [DISCUSS] JDK 1.5 for Tapestry 4.1?
>
> Every client I've talked is ready to adopt 1.5. The only reservation is
> formal support for some app servers. But I all the major vendors will
> have their products certified on 1.5 by the end of '05.
>
> In other words, I strongly support the idea. I really enjoy working on 1.5.
>
> Serge
>
>
>
> Howard Lewis Ship wrote:
> > With Tapestry 4.0 winding down, some of us are already looking forward
> > to Tapestry 4.1.
> >
> > Now, we would hope that 4.1 will not have as long a life cycle as 4.0,
> > which was 50% too long. I would hope for a final 4.1 by Q3 2006.
> >
> > One thing that I, personally, would like would be to start re-working
> > the APIs to make use of JDK 1.5 annotations and generics. Unlike the
> > add-one annotation support in Tapestry 4.0, this would MANDATE JDK 1.5
> > for development and production.
> >
> > This is obviously a contentious issue, so I'm asking people to look
> > into their personal crystal ball and see what they and they're
> > organization will look like by next summer, in terms of JDK adoption.
> >
> > --
> > 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]
> >
> >
>
> ---------------------------------------------------------------------
> 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]
