Is there a best practice document or a set of examples that demonstrate a use of Wicket Channels. I have run into a couple places in an application where the service side of obtaining data might be costly. Using an AjaxLazyLoadingPanel and/or a LoadableDetachableModel has certainly helped, but we've seen places where a blocked AJAX call prevents a longer running ajax component update from allowing the user to navigate to a different AJAX component on the screen. I'm working on an application where we have one page class with a header and footer and the main content is maintained by AJAX events. I'm wondering if channels would be helpful in some of these situations. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-Channels-best-practices-tp2294493p2294493.html Sent from the Wicket - User mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org