Ahh, I think we discussed this earlier. The best solution are to utilize a worker thread (I think) and make the client reload until the thread are done..
I think it's essential for wicket in order to handle session state to use a singleton pattern for request cycles. 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. Regards Nino -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Holmes Sent: 14. februar 2007 10:32 To: [email protected] 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 than a page constructor, would that allow a new page to be rendered while the old one is still trying to load data? -Ryan On Feb 13, 2007, at 11:19 PM, Johan Compagner wrote: > 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, Scott Lusebrink <[EMAIL PROTECTED]> wrote: 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 these constructors and onAttach methods. > While there maybe a more appropriate place for database calls to be > run, and I'd like to hear where these should be, running only 1 > page constructor at a time doesn't seem to be efficient. I've > found the code that does this. RequestCycle.874 > processEventsAndRespond(){ > // Use any synchronization lock provided by the target 874 Object > lock = getRequestTarget().getLock( this); 875 if (lock != null) > 876 { 877 synchronized (lock) 878 { 879 doProcessEventsAndRespond > (processor); 880 } 881 } > > can someone explain if this behavior is intentional, is there a way > to stop it? As a result of this behavior while a page is loading, > no other page will load until the first has finish. > I am using wicket 1.2 > > Scott > > ---------------------------------------------------------------------- > --- > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV________________________________ > _______________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
