On 2/14/07, Scott Lusebrink [EMAIL PROTECTED] wrote:
Would a WebResource not lock the rest of the application?
Not if it is defined as a shared resource. If it is component bound -
like Images use resources - it is.
Ajax is not a
possibility due to security requirements. This page is already
It sounds like Scott just wants to allow the user to cancel the
slow-loading page by navigating to another page. If his database
request happened in a LoadableDetachableModel rather than a page
constructor, would that allow a new page to be rendered while the old
one is still trying to
On 2/14/07, Ryan Holmes [EMAIL PROTECTED] wrote:
It sounds like Scott just wants to allow the user to cancel the
slow-loading page by navigating to another page.
Or at least don't show a blank page that'll provoke the user to hit
refresh ten times in a row.
If his database
request happened
. februar 2007 10:32
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] multiple rendering at same time
It sounds like Scott just wants to allow the user to cancel the
slow-loading page by navigating to another page. If his database
request happened in a LoadableDetachableModel rather
EG if page A have long loading time page b,c,d will just have to wait. So if
you utilize a worker thread then you will be able to cancel the thread and go
to the other page if you want to.
Not all requests are synced on the session though. Notably requests to
shared resources aren't, while
Im not on the dev list, I guess I can look it up on nabble?
Yep: http://www.nabble.com/stateless-behaviors-tf3226344.html
Or subscribe to it! See http://incubator.apache.org/wicket/incubator.html
Eelco
-
Take Surveys.
Thanks, that really clears it up.
At first glance, synchronizing pages on the session seems a little
overly restrictive (Scott's issue being a case in point), but of
course *not* synchronizing on the session is an infamous source of
frustrating bugs, even in frameworks with much simpler
Would a WebResource not lock the rest of the application? Ajax is not a
possibility due to security requirements. This page is already inside its
own frame, I pretty much need a unsynchronized page. Can you provide an
example of how to use a webResource to display a table
Scott
I've realized that wicket will only render one page at a time, at least it
will not run the constructor and onAttach methods of 2 pages at the same
time. This is a major bottle neck on applications with large user bases.
My app is experiencing problems because database calls are being run in
This is only true for one session. Locking means that only one page of
each session will be processed at the same time. This way we ensure that
the session state remains consisted. This is not affecting the number of
concurrent users.
-Matej
Scott Lusebrink wrote:
I've realized that wicket
the situation is that I have a page which takes a LONG time to get data for
and until that page has complete the back button or navigating to any other
page wont work. is there any way to prevent this
On 2/13/07, Scott Lusebrink [EMAIL PROTECTED] wrote:
I've realized that wicket will only
On 2/14/07, Scott Lusebrink [EMAIL PROTECTED] wrote:
the situation is that I have a page which takes a LONG time to get data for
and until that page has complete the back button or navigating to any other
page wont work. is there any way to prevent this
Let the data in the page be aggregated
poller:
http://papernapkin.org/pastebin/view/4610
example usage
http://papernapkin.org/pastebin/view/4611
-igor
On 2/13/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 2/14/07, Scott Lusebrink [EMAIL PROTECTED] wrote:
the situation is that I have a page which takes a LONG time to get
On 2/13/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 2/14/07, Scott Lusebrink [EMAIL PROTECTED] wrote:
the situation is that I have a page which takes a LONG time to get data for
and until that page has complete the back button or navigating to any other
page wont work. is there any
public class FooExport extends WebResource {
public static class Initializer implements IInitializer {
public void init(Application application) {
SharedResources res = application.getSharedResources();
res.add(foodata, new FooExport());
}
}
And the initializer
But what does that lock matter for you page if that page takes a long time?
You 'loose' the database connections for all other things anyway.
Or does that session have different windows and is displaying more then 1
page at the same time in tabs/frames or browser windows?
johan
On 2/13/07,
16 matches
Mail list logo
