Hi, On Mon, May 27, 2019 at 11:07 AM Tobias Gierke <[email protected]> wrote:
> 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 ?). > Sure! You can use Wicket WebSocket backed by a Resource. http://examples8x.wicket.apache.org/websockets/resource <http://examples8x.wicket.apache.org/websockets/resource;jsessionid=D94FD13A27B7757D34B90997FDC1BB35?0> is the demo. Source: https://github.com/apache/wicket/blob/a4b92a4322ec00832afc2fdbe2d885ca476ba6c5/wicket-examples/src/main/java/org/apache/wicket/examples/websocket/WebSocketResourceDemoPage.java#L31 > > 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 ? > No such plans. Making such change in Wicket will require *all* applications to deal with this problem by themselves. > > Cheers, > Tobias > > >
