On 10/27/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Yep, as on the tap5devwiki; basically, I'll be serializing into the form, as a single hidden field, a list of commands used to process the form submission. So instead of re-rendering the form to find all the fields and their names (query parameter names, etc.), Tapestry will be able to randomly access the necessary components to make them do their thing. Much cleaner and more efficient. Still a lot of tricky state management issues, especially w.r.t. Ajax style partial updates and other changes.
Fine, didn't look at tap5devwiki for a while... there's a lot of staff. BTW thanks Howard for the clarification. -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
