Re: Asynchronous construction of page

any progress w.r.t. to this question? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Asynchronous-construction-of-page-tp1892224p2270690.html Sent from the Wicket - User mailing list archive at Nabble.com

Re: Asynchronous construction of page

>> of Wicket? Is there maybe another approach available (one that still >>> uses Wicket for the parts)? >>> >>> Thanks, >>> Kaspar >>> >>> - &

Re: Asynchronous construction of page

t; Kaspar >> >> - >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >&g

Re: Asynchronous construction of page

t; uses Wicket for the parts)? > > Thanks, > Kaspar > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > -- View

Re: Asynchronous construction of page

On 02.11.2009, at 22:59, Igor Vaynberg wrote: > if you want nonblocking you have to make each thing you are trying to > load asynchronously its own page inside an iframe. > > the page itself can only be accessed synchronously, otherwise you > would have to do your own multithreaded access handli

Re: Asynchronous construction of page

That's what I ended up doing (basically like ). 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 thre

Re: Asynchronous construction of page

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 wrote: > Because the requests will be sequential (a prob

Re: Asynchronous construction of page

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 laz

Re: Asynchronous construction of page

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 On Thu, Nov 5, 2009 at 6:00 PM, Kaspar Fischer wrote: > On 05.11.2009, at 03:06, jpswain wrote: > > Wicket is remark

Re: Asynchronous construction of page

work > synchronously. Is this still the case with the latest version/snapshot > of Wicket? Is there maybe another approach available (one that still > uses Wicket for the parts)? > > Thanks, > Kaspar > > -- View this message in context: http://old.nabble.com/Asynch

Re: Asynchronous construction of page

One question: if component renderComponent method wasn't final if Kaspar page structure was -page - panel1 - paneln if page renderComponent method implementation was buildPanel1.start() buildPaneln.start() and renderClosingComponentTag implementation was allPanelReady.join() super.(...)

Re: Asynchronous construction of page

On 02.11.2009, at 22:59, Igor Vaynberg wrote: the page itself can only be accessed synchronously, otherwise you would have to do your own multithreaded access handling in components...which would be horrific. It's definitely not nice and it would be cool if there were some way to do this in

Re: Asynchronous construction of page

I will try to use pages in iframes then. Thanks a lot, Igor. Kaspar On 02.11.2009, at 22:59, Igor Vaynberg wrote: if you want nonblocking you have to make each thing you are trying to load asynchronously its own page inside an iframe. the page itself can only be accessed synchronously, otherwi

Re: Asynchronous construction of page

if you want nonblocking you have to make each thing you are trying to load asynchronously its own page inside an iframe. the page itself can only be accessed synchronously, otherwise you would have to do your own multithreaded access handling in components...which would be horrific. -igor On Mon

Asynchronous construction of page

I am trying to find out how to load several parts (Wicket panels) of a page in parallel using Ajax. The content of these parts takes long to render but I still want the user to see the other, readily available parts of the page, with the delayed panels appearing when available. Several post