Hi Korbinian,
Wicket Ajax is primarily used for UI updates, thus all requests *have*
to be sent sequentially: Otherwise user input
(click...tab...type...click...click) would not be processed in a
deterministic way!
Furthermore all requests are queued on the server too (each page is
locked sep
On Wed, Aug 14, 2019 at 10:19 AM Sven Meier wrote:
> Hi Korbinian,
>
> Wicket Ajax is primarily used for UI updates, thus all requests *have*
> to be sent sequentially: Otherwise user input
> (click...tab...type...click...click) would not be processed in a
> deterministic way!
> Furthermore all r