Ok thanks Martijn for the clarification.
On Mon, Nov 16, 2015 at 2:06 PM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:
> Well, you can create a Wicket resource for the updates to avoid a
> pagemap lock, but it is essentially the price we pay for having a
> singe-threaded access to the co
Well, you can create a Wicket resource for the updates to avoid a
pagemap lock, but it is essentially the price we pay for having a
singe-threaded access to the component hierarchy.
You can also create a servlet, but both options will block a thread on
your server waiting for the processing to fin
Hi Martijn,
are you basically saving that with wicket there is no way I can not avoid
the pagemap locking for a given ajax or iframe request when needed?
BTW web sockets aren't supported in IE8.
On Mon, Nov 16, 2015 at 1:47 PM, Martijn Dashorst <
martijn.dasho...@gmail.com> wrote:
> you probabl
you probably should look into websockets if you don't want polling.
Martijn
On Mon, Nov 16, 2015 at 12:50 PM, Wayne W wrote:
> Hi,
>
> I have a page that has a AbstractDefaultAjaxBehavior which adds a new panel
> in the ajax request. This new panel can be a long running process to
> generate som
Hi,
I have a page that has a AbstractDefaultAjaxBehavior which adds a new panel
in the ajax request. This new panel can be a long running process to
generate some data. I'm find this is locking the page map so other requests
on that page get locked.
How could I get around this aside from re-engin
