On Wed, Jan 13, 2016 at 10:18 AM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:

> Hi Martin!
>
> Thanks for the supper fast answer! What I need is something like
>
> 1- On client side: you say stop this request and by doing so I unlock the
> page and make it ready to accept new AJAX request
> 2- Fire a new AJAX request
>
>
> > Wicket's AjaxChannels manage the waiting requests only. Once a request is
> > fired you cannot do anything.
> >
> > I see. I will still have a server side lock on the page from previous
> request? I guess... So, my new AJAX request (on a new channel) will not
> fire till server side finish rendering first request :-(
>

That's correct!


>
>
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Wed, Jan 13, 2016 at 9:59 AM, Ernesto Reinaldo Barreiro <
> > reier...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > Happy 2016 to all wicketeers!
> > >
> > > Going to business: is there a way to cancel an ongoing AJAX request
> when
> > a
> > > new one is triggered? This last thing conditional (i.e. not for all new
> > > AJAX requests but certain). Is using a different channel enough?
> > >
> > > Thanks in advance
> > >
> > > --
> > > Regards - Ernesto Reinaldo Barreiro
> > >
> >
>
>
>
> --
> Regards - Ernesto Reinaldo Barreiro
>

Reply via email to