[ 
http://issues.apache.org/jira/browse/JS2-226?page=comments#action_12431780 ] 
            
Woonsan Ko commented on JS2-226:
--------------------------------

David,

Thanks for your comment. I'm very happy with your insights. 
Very important clues from you:
 - Defered rendering for late-rendering portlets is possible. (Worker can store 
the late content for later use.)
 - Portlets can be marked as parallel processing.
 - Jetspeed Desktop can be a good alternative.

On the other hand, I think my idea has some problems like the following:
 - If some portlets are parallel and otheres are not, then the current threads 
are not worker thread only. If a current thread is one of the servlet 
container, then we cannot store attributes in that. I need to have a solution 
for this.

Also I think:
 - Defered rendering has no problem. I think the aggregator can do that 
according to portlet definitions.
 - I think Jetspeed Desktop is one of the best solutions for PC-based browser 
clients. However, the server-side solution is meaningful, as David said.

By the way, I have a question. There are two classes, PageAggregatorImpl and 
AsyncPageAggregatorImpl. Which is proper, PageAggregatorImpl with parallel 
option or AsyncPageAggregatorImpl?
I guess PageAggregatorImpl is more adequate because it has to support portlets 
marked as parallel. Am I right?

I will post my test patches when I finish cleaning my messy codes. (about until 
September 8.)
Thanks again, David.

> Page Aggregation using STRATEGY_PARALLEL severly broken
> -------------------------------------------------------
>
>                 Key: JS2-226
>                 URL: http://issues.apache.org/jira/browse/JS2-226
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Aggregation
>    Affects Versions: 2.1
>         Environment: Tomcat 5.0.28
>            Reporter: Ate Douma
>         Assigned To: David Sean Taylor
>            Priority: Critical
>
> While trying to evaluate the status of JS2-17 I tested PageAggregation with 
> PageAggregatorImpl.STRATEGY_PARALLEL and the effect is a total breakdown!
> I'll look into this AFTER the M2 release.
> Not sure if the current problem is related to JS2-17 but I'll check that too.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to