You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Sergey Didenko <se...@gmail.com> on 2009/04/12 19:19:13 UTC
Re: [DISCUSS] JavaScript, Degradation, Page Load, Script Placement
Sorry if I ask a silly question, i'm a newbie to Tapestry.
You mention there were race conditions on slow connections. How were
they possible?
If a page is rendering then it has already processed its handlers. So
when a browser gets a half of the page, all the related handlers
already finished their work, right? So what thing races with what?
Regards, Sergey.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [DISCUSS] JavaScript, Degradation, Page Load, Script Placement
Posted by Howard Lewis Ship <hl...@gmail.com>.
By the time any markup is sent to the browser, the page will be
finished rendering. Tapestry renders to a DOM then streams the DOM.
Persistent fields will already be in the session, ready to be pulled
out against a new page instance.
On Mon, Apr 13, 2009 at 12:39 PM, Sergey Didenko
<se...@gmail.com> wrote:
> BTW, can't race conditions happen in the following case:
>
> A client without Javascript clicks on ActionLink before the page
> finishes loading.
>
> ?
>
> This does not seem like it can be handled with the help of Javascript.
>
> On Sun, Apr 12, 2009 at 8:43 PM, Sergey Didenko
> <se...@gmail.com> wrote:
>> Does it race when "render" request uses an object from HttpSession and
>> concurrent "action" request changes that object?
>>
>> If so, can't it be handled on server? I'm worring that the current
>> client-based approach is going to be overcomplicated.
>>
>> On Sun, Apr 12, 2009 at 8:19 PM, Sergey Didenko
>> <se...@gmail.com> wrote:
>>> Sorry if I ask a silly question, i'm a newbie to Tapestry.
>>>
>>> You mention there were race conditions on slow connections. How were
>>> they possible?
>>>
>>> If a page is rendering then it has already processed its handlers. So
>>> when a browser gets a half of the page, all the related handlers
>>> already finished their work, right? So what thing races with what?
>>>
>>> Regards, Sergey.
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
Director of Open Source Technology at Formos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [DISCUSS] JavaScript, Degradation, Page Load, Script Placement
Posted by Sergey Didenko <se...@gmail.com>.
BTW, can't race conditions happen in the following case:
A client without Javascript clicks on ActionLink before the page
finishes loading.
?
This does not seem like it can be handled with the help of Javascript.
On Sun, Apr 12, 2009 at 8:43 PM, Sergey Didenko
<se...@gmail.com> wrote:
> Does it race when "render" request uses an object from HttpSession and
> concurrent "action" request changes that object?
>
> If so, can't it be handled on server? I'm worring that the current
> client-based approach is going to be overcomplicated.
>
> On Sun, Apr 12, 2009 at 8:19 PM, Sergey Didenko
> <se...@gmail.com> wrote:
>> Sorry if I ask a silly question, i'm a newbie to Tapestry.
>>
>> You mention there were race conditions on slow connections. How were
>> they possible?
>>
>> If a page is rendering then it has already processed its handlers. So
>> when a browser gets a half of the page, all the related handlers
>> already finished their work, right? So what thing races with what?
>>
>> Regards, Sergey.
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [DISCUSS] JavaScript, Degradation, Page Load, Script Placement
Posted by Sergey Didenko <se...@gmail.com>.
Does it race when "render" request uses an object from HttpSession and
concurrent "action" request changes that object?
If so, can't it be handled on server? I'm worring that the current
client-based approach is going to be overcomplicated.
On Sun, Apr 12, 2009 at 8:19 PM, Sergey Didenko
<se...@gmail.com> wrote:
> Sorry if I ask a silly question, i'm a newbie to Tapestry.
>
> You mention there were race conditions on slow connections. How were
> they possible?
>
> If a page is rendering then it has already processed its handlers. So
> when a browser gets a half of the page, all the related handlers
> already finished their work, right? So what thing races with what?
>
> Regards, Sergey.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org