The crux of the matter so far was the AjaxBehavior which wasn't stateless. We
will use Wicket 7.4.0 from now on and try to make all relevant pages
stateless.
I found this part of the documentation, which is quite new
https://github.com/apache/wicket/blob/master/wicket-user-guide/src/docs/guide/ajax/ajax_7.gdoc
and a good starting point for refactoring our application.
Thank you Martin.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Concerns-about-different-render-strategies-and-latency-tp4675545p4675556.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
