[
https://issues.apache.org/jira/browse/WICKET-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748418#action_12748418
]
Rodrigo De Castro commented on WICKET-2437:
-------------------------------------------
So, is there any plan to make pages thread-safe or does it require an
architecture change? Otherwise, it seems to defeat the whole purpose of making
things async with Ajax. I would be interested in trying to fix that, so please
let me know how I can help.
In the meanwhile, should I turn them into individual pages and use an external
Ajax library to load them in async way? What would be your suggestion if I have
an application with multiple AjaxLazyLoadPanel and I need to paralyze the
requests?
> Ajax requests are called serially using only one channel (Channel busy -
> postponing...)
> ---------------------------------------------------------------------------------------
>
> Key: WICKET-2437
> URL: https://issues.apache.org/jira/browse/WICKET-2437
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 1.4.0
> Reporter: Rodrigo De Castro
> Assignee: Matej Knopp
>
> I have several lazy load panel that load DynamicImageResource objects. They
> are always loaded in serial mode. These are the debug messages:
> INFO: Initiating Ajax GET request on
> ../?wicket:interface=:3:tabpanel:panel:app_graph_panel:1:graph::IBehaviorListener:0:1&random=0.7774967316771
> INFO: Invoking pre-call handler(s)...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Channel busy - postponing...
> INFO: Received ajax response (2665 characters)
> After checking the code, it seems that every Ajax code in Wicket does not
> specify the channel when calling wicketAjaxGet. By doing that, all the
> requests end up in the default queue, being executed serially.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
