this has been discussed many times on the list, search the archives...
-igor
On Wed, Dec 14, 2011 at 9:20 AM, Karen Schaper karen.scha...@gmail.com wrote:
Hi,
A user was testing a web application.
Apparently they clicked on a link that opened a report and quickly
clicked the link again.
Once the user has clicked a link to another page (Or switched a tab if it is
a tabed page), is there a way to terminate the request to prevent a load on
the server for a page that will not be displayed?
Normally: no, because these are separate requests. The first request will
cancel only when
Actually using lazy panel makes the problem worse, now the user can click on
the tabs, but they will not work as they wait to the lazy panel to
complete...
We need to allow to move to another tab, without waiting for the first tab
to be rendered.
--
View this message in context:
If you are using wicket 1.4, you should be able to delegate your long
running request to work with a different pageMap.
On Mon, Oct 24, 2011 at 6:16 AM, YaronHolland [via Apache Wicket]
ml-node+s1842946n3932536...@n4.nabble.com wrote:
Actually using lazy panel makes the problem worse, now the
How can i delegate to another PageMap when i need it on a panel in a tabed
page?
The PageMap is declared in the page, how can i use a diffrent PageMap for a
tab in the page?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/PageMap-locking-tp3930623p3932904.html
Sent
you shouldnt have requests that take a long time to process. there are
lots of problems with this like users starving your threadpool, etc.
instead you should load the data in another thread and either use a
push notification or let the client poll to find out if the data is
available.
most likely this concurrent access happens when you are iterating over
pages in the pagemap and invoking listeners on them and another thread
access one of the pages you are iterating over. you will have to lock
your iteration loop on the same lock wicket uses. as a rule of thumb
we do not
yeah, that's why I thought that I would be safe when only dispatching events
during the request processing to a page from the page-map.
thanks, Frank
On Wed, Apr 28, 2010 at 4:48 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
most likely this concurrent access happens when you are iterating
Why would you want your users to wait for 1 minute to get results? On
what planet and time/space continuum do you expect users to wait for
that?
Don't do the computation in the request thread. Compute the stuff in a
separate thread, process or whatever and subscribe the user's
