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.fisc...@dreizak.com>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-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
--
Pedro Henrique Oliveira dos Santos
