That's what I ended up doing (basically like <http://blog.miau.biz/2008/12/wicket-and-slow-running-process-in.html>).
I just wanted to explain to Pieter why ... On 28.11.2009, at 11:27, Johan Compagner wrote: > load that data in separate threads, dont touch any wicket components > in those threads > make a component like ajaxlazyload that polls for that data if still > not there use a timer of a few seconds to test it again > > On 28/11/2009, Kaspar Fischer <kaspar.fisc...@dreizak.com> wrote: >> Because the requests will be sequential (a problem in general but not so >> much in my case) and because I have an auto-completion field on the same >> page. As I understand it, having some AjaxLazyLoadPanel's active on my page, >> the auto-completion requests will be queued. So if the loading of the lazy >> panels takes time, the user experiences slow response in the auto-completion >> field. Please correct me if I am wrong. >> >> Kaspar >> >> On 06.11.2009, at 08:47, Pieter Degraeuwe wrote: >> >>> Why don't you use the AjaxLazyLoadPanel for each part the the screen that >>> takes some time to load? (see also at >>> http://www.roseindia.net/tutorials/wicket/lazy-load.shtml) >>> >>> Pieter --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
