if the table is the only expensive component on your page then there is really no advantage to using ajax since you are adding all the overhead of javascript processing without saving anything.
-igor On Tue, Jun 3, 2008 at 3:57 AM, Niels Bo <[EMAIL PROTECTED]> wrote: > > Hi > > I have observed that using AJAX to update of large content of a page is much > slower than > updating the full page withou AJAX. For example AJAX sorting a big DataTable > (10x25) can be much slower that without AJAX, and I often see "Client > parsetime" of more than a second in IE. > FireFox seems to be faster, so I am hoping that is is possible to optimize > the Wicket AJAX Javascript. > > Is this somthing that you Wicket developers will look into? > > Best Regards > Niels > -- > View this message in context: > http://www.nabble.com/AJAX-slower-than-full-page-update-tp17620961p17620961.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
