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

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.

 

Reply via email to