Wicket always locks session for requests, so it always waits until the page is processed. Worker thread could help in this case.
-Matej Nino Wael wrote: > Hi > > > > On one of our pages I’ve created at cancel button. The functionality are > simple, im just doing some simple javascript that reloads the url, > however it looks like wicket waits for the original request to complete > before loading the new page(hence the cancel button no longer has the > desired effect, user still has to wait for the original request to > load). Are there anyway to avoid this? > > > > Or do I have to incorporate a worker thread(and do some nifty ajax > maybe), so that it actually can be cancelled. > > > > > > Regards Nino > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > 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
