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-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
