I think users are less forgiving than Wicket :) Martijn
On Wed, Jul 23, 2008 at 12:05 PM, Erik van Oosten <[EMAIL PROTECTED]> wrote: > > O, I forgot, be aware that Wicket does not really tolerate pages that take > too long to render. Make sure that the page rendering does not take more > then 60 seconds in total. (Luckily the Future#get method accepts a timeout > argument.) > > > Erik van Oosten wrote: >> >> ...dump all your Callables in a ExecutorService >> and when that is done call get() on the returned Futures... >> > > Regards, > Erik. > > -- > View this message in context: > http://www.nabble.com/Asynchronous-Components-tp18598968p18607531.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
