> 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 you can easily trick shared resources to actually handle client specific requests. The only thing you'd miss there is the markup handling/ rendering you would have with normal page requests. Also: see my email about stateless behaviors (and the question whether we synchronize stateless pages on the session - which we shouldn't imo - to the dev list). Eelco ------------------------------------------------------------------------- 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
