Hi,
This will remove the serialization at the client side (JavaScript) but
there is also synchronization at the server side - only one request
can work with the same page instance.
I guess this is where they wait each other.
On Wed, Oct 24, 2012 at 4:32 PM, danisevsky <danisev...@gmail.com> wrote:
> Hi,
>
> I have long-running ajax behavior. And when this behavior is running
> no other ajax component on page can work because ajax requests are
> serial. My question is if it is possible to use another ajax channel
> for long-runnig behavior?
>
> I tried:
>
> @Override
> protected void updateAjaxAttributes(AjaxRequestAttributes attributes)
> {
> attributes.setChannel(new AjaxChannel("another"));
> }
>
> but this didn't work (ajax requests are still serial). I am using wicket 6.
>
> Thanks in advance!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
