portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Commented: (JS2-755) Desktop Pipeline: Blank deley when switch page
Date Thu, 30 Aug 2007 00:56:30 GMT

    [ https://issues.apache.org/jira/browse/JS2-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523742
] 

Woonsan Ko commented on JS2-755:
--------------------------------

Yes, it is still async rendering, and it is still client side parallel rendering, of course.
I just suggested that it would be better to put portlet windows one by one, row by row.
There's no difference on asynchronous DOJO bindings between the existing and my suggestion.

The existing implementation works like the following:
 - Reads psml.
 - Creates all portlet windows.
 - Renders all portlet windows. (Iterates all portlet windows and invokes DOJO binding, which
makes asynchronous call. That is, it invokes sequentially, but retrieves portlet contents
asynchronously by using asynchronous DOJO binding.)

My suggestion works like the following:
 - Reads psml. Register a timer. 
 - [LOOP until there remains portlet windows] 
      When it is on timer, create a portlet window and render the portlet window. Register
a new timer.
 - Of course, rendering means invoking asynchronous DOJO binding, so it renders asynchronously.
 - Why timer using window.setTimeout()?
     If we create and render in a loop without timers, then browsers have a difficulty to
get a chance to render UI.  In that case, all portlet windows look rendered at the same time.
So I think we should relieve browsers by using window.setTimeout().

During my testings with my patch, I got the following approximate figures:

[Test scenario]
In the '/jetspeed.psml' page, click the '/default-page.psml'.

[Firefox 2.0.0.6]
The existing: 12 sec. to show all portlet windows. (All portlet windows were rendered almost
at the same time.)
My patch: 2 sec. to show upper 4 portlet windows. 8.5 sec. to show all portlet windows.
                  Also, it shows the first portlet window faster.

[IE 6]
The existing: 13 sec. to show all portlet windows. (All portlet windows were rendered almost
at the same time.)
My patch: 5 sec. to show upper 4 portlet windows. 14 sec. to show all portlet windows.
                  Also, it shows the first portlet window faster.

Thanks!

> Desktop Pipeline: Blank deley when switch page
> ----------------------------------------------
>
>                 Key: JS2-755
>                 URL: https://issues.apache.org/jira/browse/JS2-755
>             Project: Jetspeed 2
>          Issue Type: Improvement
>    Affects Versions: 2.1.2
>         Environment: Tomcat5.5, IE6 and FF2.0.0.4
>            Reporter: Yang Sie
>            Assignee: Steve Milek
>             Fix For: 2.1.3, 2.2
>
>         Attachments: JS755.diff
>
>
> When I shifted from one page to another, say from 'registration' to 'Welcome to Jetspeed
2', there is a short blank delay (i.e. while the 'welcome to jetspeed 2' tab is on focus right
after clicking the tab, the content shows blank from some 2 to 3 sec. before all portlet fragment
start to show (start with loading... on the portlet action bar and then full contents...)).


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message