Hi,
Wicket pages are single threaded, so no - you can't render multiple
panels concurrently.
You should restructure you code so that the health checks are done
asynchronously. The panels just check for the availability, and render
some progress indicator as long as no data is available.
Regards
Sven
On 14.06.2015 11:04, Robert Gründler wrote:
Hi,
our backend application has a page containing ~20 panels which render
health-checks of different components in our
infrastructure. Each one of these checks can take some time (~ 10 seconds)
until it timeouts if the background-component
is not reachable.
Until now we’ve used AjaxLazyLoadingPanels to render those panels, but due to
the fact, that wicket can only run
one ajax request at a time on a single page, this can result in extremely long
loading times until all panels are displayed.
I’ve tried to implement the panel rendering using websockets - but it seems i’m
running in the same problem like the concurrent
ajax request issue - meaning that when i spawn the loading of the expensive
panel in the background, which page instance
should i use to render the panel?
So my question is: Is there a way to render multiple panels concurrently in
wicket? Which each panel having it’s own timeout?
regards
robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
