You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Jonathan Barker <jo...@gmail.com> on 2017/06/24 19:10:33 UTC
Zone update 5.3-5.4 timing changes
Hello all,
We are in the midst of an upgrade of an application from 5.3.7 to
5.4.x, and we have hit a snag. Actions that were previously
near-instantaneous now wait until the completion of zone loads.
This is a dashboard page that makes extensive use of Progressive
display to get the initial page displaying quickly and then having
database intensive (sometimes slow) updates to parts of the page
happening after that.
With 5.3.x, even with some particularly slow zones still loading,
there was no problem opening up a float box to either do a search, or
set new date restrictions.
With 5.4, all of the zones need to have completed their updates before
there is any reaction to clicks on the two links mentioned. Both of
these cases rely on Ajax, and if a link to some other page or site is
substituted, it is followed immediately. Any clicks are "cached" and
result in multiple float box loads when they finally do occur.
We need to have the near-immediate response and not have to wait until
all displays have loaded,
Any thoughts or suggestions?
--
Jonathan Barker
ITStrategic
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Zone update 5.3-5.4 timing changes
Posted by Jonathan Barker <jo...@gmail.com>.
Unfortunately, there are not. I could arrange a join.me session at
your convenience if you are willing.
On Mon, Jun 26, 2017 at 1:16 PM, Thiago H. de Paula Figueiredo
<th...@gmail.com> wrote:
> Hi!
>
> Is there any publicly-accessible page demonstrating this behavior?
>
> On Sat, Jun 24, 2017 at 4:10 PM, Jonathan Barker <
> jonathan.theitguy@gmail.com> wrote:
>
>> Hello all,
>>
>> We are in the midst of an upgrade of an application from 5.3.7 to
>> 5.4.x, and we have hit a snag. Actions that were previously
>> near-instantaneous now wait until the completion of zone loads.
>>
>> This is a dashboard page that makes extensive use of Progressive
>> display to get the initial page displaying quickly and then having
>> database intensive (sometimes slow) updates to parts of the page
>> happening after that.
>>
>> With 5.3.x, even with some particularly slow zones still loading,
>> there was no problem opening up a float box to either do a search, or
>> set new date restrictions.
>>
>> With 5.4, all of the zones need to have completed their updates before
>> there is any reaction to clicks on the two links mentioned. Both of
>> these cases rely on Ajax, and if a link to some other page or site is
>> substituted, it is followed immediately. Any clicks are "cached" and
>> result in multiple float box loads when they finally do occur.
>>
>> We need to have the near-immediate response and not have to wait until
>> all displays have loaded,
>>
>> Any thoughts or suggestions?
>>
>>
>> --
>> Jonathan Barker
>> ITStrategic
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
> --
> Thiago
--
Jonathan Barker
ITStrategic
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Zone update 5.3-5.4 timing changes
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Hi!
Is there any publicly-accessible page demonstrating this behavior?
On Sat, Jun 24, 2017 at 4:10 PM, Jonathan Barker <
jonathan.theitguy@gmail.com> wrote:
> Hello all,
>
> We are in the midst of an upgrade of an application from 5.3.7 to
> 5.4.x, and we have hit a snag. Actions that were previously
> near-instantaneous now wait until the completion of zone loads.
>
> This is a dashboard page that makes extensive use of Progressive
> display to get the initial page displaying quickly and then having
> database intensive (sometimes slow) updates to parts of the page
> happening after that.
>
> With 5.3.x, even with some particularly slow zones still loading,
> there was no problem opening up a float box to either do a search, or
> set new date restrictions.
>
> With 5.4, all of the zones need to have completed their updates before
> there is any reaction to clicks on the two links mentioned. Both of
> these cases rely on Ajax, and if a link to some other page or site is
> substituted, it is followed immediately. Any clicks are "cached" and
> result in multiple float box loads when they finally do occur.
>
> We need to have the near-immediate response and not have to wait until
> all displays have loaded,
>
> Any thoughts or suggestions?
>
>
> --
> Jonathan Barker
> ITStrategic
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Thiago