On Wed, Feb 24, 2010 at 1:26 PM, Corbin, James <[email protected]> wrote: > I'm profiling our Wicket Application using Google's Speed Tracer Plugin > (nice plugin). > > > > The profiling tool is showing most of the time spent in two areas, > > > > 1) Parsing HTMlL
this measures the browser's speed not wickets.... besides, where does most of the time browserside should go? shouldnt it be parsing html? thats what browsers do... -igor > > 2) Javascript Valuation (mostly with YUI). > > > > What are some of the best practices around developing code that > minimizes the impact of parsing HTML in Wicket? > > > > We haven't had a lot of time to optimize our code and now are starting > to look at that aspect of our application. > > > > Thanks, > > > > J.D. > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
