well, i'm not expecting ajax to take over the world or replace the normal webapp any time soon. however, i think that there are many situations where ajax could be a great fit and i'm excited by the fact that tapestry is posed to be one of the first frameworks to enable easy(er) ajax app development. in my own work i can think of a number of examples where ajax would be a terrible choice and i can also think of a number of others where ajax would not only be a good solution but would blow the clients socks off. for instance, an ajax-based content management system could be *very* cool. we've already done some ajax here but only on the individual component scale.
On Thu, 2005-12-01 at 14:41 -0500, Jesse Kuhnert wrote: > I'm sorry Konstantin..I should have been more clear about my > intentions..They are only to make all of these things easier to use in > tapestry, but on an optional basis. Ie it won't be on by default and will be > a completely optional choice that people make depending on their own needs. > > jesse > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
