Asynchronous construction of page

[Kaspar Fischer-2]

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 posts on this list indicate that AjaxLazyLoadPanel's only 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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[igor.vaynberg]

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, Nov 2, 2009 at 1:32 PM, Kaspar Fischer
<kaspar.fischer@...> wrote:

> 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 posts on this list
> indicate that AjaxLazyLoadPanel's only 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Kaspar Fischer-2]

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, otherwise you
> would have to do your own multithreaded access handling in
> components...which would be horrific.
>
> -igor
>
> On Mon, Nov 2, 2009 at 1:32 PM, Kaspar Fischer
> <kaspar.fischer@...> wrote:
>> 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 posts on  
>> this list
>> indicate that AjaxLazyLoadPanel's only 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
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Kaspar Fischer-2]

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 Wicket without having to spawn a thread from the HTTP  
request itself.

Nonetheless, here's a blog post on handling requests in separate  
threads:

   http://blog.miau.biz/2008/12/wicket-and-slow-running-process-in.html

Kaspar

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Pedro H. O. dos Santos]

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.(...)

and if the buildPanel1 thread implementation write to response the component
html on it finish?
Only a very crude idea... can it work?

On Wed, Nov 4, 2009 at 4:09 PM, Kaspar Fischer
<kaspar.fischer@...>wrote:

>
> 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 Wicket without having to spawn a thread from the HTTP request
> itself.
>
> Nonetheless, here's a blog post on handling requests in separate threads:
>
>  http://blog.miau.biz/2008/12/wicket-and-slow-running-process-in.html
>
>
> Kaspar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
Pedro Henrique Oliveira dos Santos

[jpswain]

Wicket is remarkably fast and efficient the way it is used in common practice.  To do what you are suggesting would be to wreck that big time.  Why on earth do you want to do this?

Kaspar Fischer-2 wrote:

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 posts on this list indicate that AjaxLazyLoadPanel's only 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

[Kaspar Fischer-2]

On 05.11.2009, at 03:06, jpswain wrote:

> Wicket is remarkably fast and efficient the way it is used in common
> practice.  To do what you are suggesting would be to wreck that big  
> time.
> Why on earth do you want to do this?

I am very happy with Wicket's speed but sometimes the data that needs  
to be displayed by Wicket is not readily available. In my application,  
I need to do display the results of several calculations, each of  
which may require a different amount of time. Unfortunately, there is  
not a lot to cache. -- I want to display to the user a page right away  
and as the results come in, in whatever order, show them.

Kaspar

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Pieter Degraeuwe]

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
<kaspar.fischer@...>wrote:

> On 05.11.2009, at 03:06, jpswain wrote:
>
>  Wicket is remarkably fast and efficient the way it is used in common
>> practice.  To do what you are suggesting would be to wreck that big time.
>> Why on earth do you want to do this?
>>
>
> I am very happy with Wicket's speed but sometimes the data that needs to be
> displayed by Wicket is not readily available. In my application, I need to
> do display the results of several calculations, each of which may require a
> different amount of time. Unfortunately, there is not a lot to cache. -- I
> want to display to the user a page right away and as the results come in, in
> whatever order, show them.
>
> Kaspar
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
Pieter Degraeuwe
Systemworks bvba
Belgiëlaan 61
9070 Destelbergen
GSM: +32 (0)485/68.60.85
Email: pieter.degraeuwe@...
visit us at http://www.systemworks.be