Howard, can't these major changes be wrapped up in single point releases?
4.1: Delete the rewind cycle
4.2: Rework component interfaces..
and such??
Q3 2006 seems like a lot! Almost a year..
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Howard Lewis Ship wrote:
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
