From wicket source code WebRequestCycleProcessor has a lock on session.
(Look at the source code below).
From a profiler we can easily observe that %57 of the time is spent on this
function especially on lock region.
Is there any way to speed it up this source code ?
/**
* @see
can you submit a quickstart that reproduces this?
the lock on session only blocks concurrent requests from the browser,
which is usually not a big deal because most users operate one window
at a time.
also we do not get the same results in our wicket-threadtest project.
-igor
On Tue, Nov 10,
Hi
There are parts in web which make ajax calls. In this situtation on request
blocks the piece of code till it returns a value. Do you recommend anything
about ajax calls in a web page?
Thanks
Pamir
On Tue, Nov 10, 2009 at 9:28 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
can you submit a
Could you please send me a link that how i can achieve this over wicket ?
On Wed, Nov 11, 2009 at 1:18 AM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
well, its either we lock on the page, or you have to make sure all
your code is threadsafe.
yes, this can be a problem for a lot of
search this list, google it. this has been answered on this list multiple times.
-igor
On Tue, Nov 10, 2009 at 3:22 PM, Pamir Erdem pamir.er...@gmail.com wrote:
Could you please send me a link that how i can achieve this over wicket ?
On Wed, Nov 11, 2009 at 1:18 AM, Igor Vaynberg
well, its either we lock on the page, or you have to make sure all
your code is threadsafe.
yes, this can be a problem for a lot of concurrent ajax requests, you
just have to make sure your responses are fast. eg if you have a
time-consuming operation do it in a background thread and make ajax
