Page lock & performance

[Tobias Gierke]

Hi,

In the past I've been bitten a (very) few times by performance issues 
caused by the "only one ongoing request per Page instance per session" 
limitation in Wicket.

My use-cases were:

1.) displaying a huge number (>100) of dynamically rendered images 
(charts) on a single page
2.) displaying a "dashboard"-style page with a number of individual 
panels that each refresh independently

Case 1.) I solved with a hacky solution that puts the images into a 
HashMap served by a tiny servlet and using links pointing to the servlet 
instead of using DynamicImage in the generated markup
For case 2.) I couldn't come up with a solution yet (maybe someone else 
solved this already ?).

Not sure if this is even possible with the current architecture of 
Wicket - but are there any plans to make wicket-core thread-safe so 
Components could serve requests in parallel ?

Cheers,
Tobias