Let me try an example. Take a pretty rich web app like markmail: http://tapestry.markmail.org/search/?q=tapestry
When you search on markmail, it causes a whole page refresh. (not what I'm trying to do). But, what if instead it updated just the applicable components on the page, such as the search results, using Ajax? This is basically what I'm trying to accomplish with my web app. In general, I think one could argue that the 'richer' your application becomes (fatter webpages with alot of Ajax), the higher chance you might want something like this. I think there are less common usecases why this would be useful for more traditional web apps. Seth Thiago H. de Paula Figueiredo wrote: > > On Mon, May 18, 2009 at 12:47 PM, ownedthx <sethc...@gmail.com> wrote: >> One note: I'm avoiding using zone updates to >> orchestrate this cross-component behavior, because in my understanding, >> the >> bulk of the logic has to then live in Javascript in the client. > > Why? Just curious. :) > > -- > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > -- View this message in context: http://www.nabble.com/In-Ajax-request-to-component-causing-another-component-a-chance-to-render-tp23599118p23601157.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
