I'm pretty happy with how it came out; I think my original thinking for Ajax was that it would be driven primarily from the client side, and this one is driven more from the server side. Ajax is one area where you do have to be somewhat aware of client-side ids, typically, Ajax zones should be configured with a specific id to make sure things work. There's definitely some scalability advantages of doing all the rendering (including JavaScript generation) in a single go, rather than chaining a series of Ajax requests together.
On Mon, Mar 9, 2009 at 7:54 AM, Massimo Lusetti <[email protected]> wrote: > On Sat, Mar 7, 2009 at 12:43 AM, <[email protected]> wrote: > >> Author: hlship >> Date: Fri Mar 6 23:43:41 2009 >> New Revision: 751140 >> >> URL: http://svn.apache.org/viewvc?rev=751140&view=rev >> Log: >> TAP5-108: A component event handler for Ajax requests should have a >> mechanism to update mutiple zones on the client > > I've had the opportunity to only look at the code and not test it but > this seems really cool. > > Thanks > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
