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 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? No, that doesn't make a difference. Detachable models can be used to limit the amount of data that is cached as 'component state' between requests, and to ensure that new requests are done with fresh data. The rendering of pages stands apart from that. If you want to break up a request in multiple parts - which is what you want to do here, as you first want to show the page without the data, possibly with some kind of place holder for the data or e.g. a progress indicator - you can best use Ajax or, second best, use (i)frames and resources. If you use Ajax, it's best to do the processing in a separate thread and let Ajax do polling as that won't block the session. Which reminds me of something I wanted to investigate concerning stateless behaviors (for ajax). But I'll start another thread about that. 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
