[ http://issues.apache.org/jira/browse/COCOON-1709?page=all ]
Jean-Baptiste Quenot updated COCOON-1709:
-----------------------------------------
Attachment: 20051222-MapProfileLS.java
Update the patch:
* check the validity of profiles
* clone layout like what is done for copletinstancedata
Updated patch contributed by Philippe Gassmann <[EMAIL PROTECTED]>
> Speedup portal loading
> ----------------------
>
> Key: COCOON-1709
> URL: http://issues.apache.org/jira/browse/COCOON-1709
> Project: Cocoon
> Type: Improvement
> Components: Blocks: Portal
> Versions: 2.1.9-dev (current SVN)
> Reporter: Jean-Baptiste Quenot
> Attachments: 20051212-portal-MapProfileLS, 20051222-MapProfileLS.java
>
> Portal loads user profiles (when using eg AuthenticationProfileManager) with
> Castor every time the user logs in and this is very slow. This patch allows
> to cache the result for further invocations. However the coplet instance
> profiles are handled in a special way, after being obtained by mapping the
> CopletInstanceDataManager they are cloned to ensure that every user gets its
> own copy of the coplets. Thus this bug depends on
> http://issues.apache.org/jira/browse/COCOON-1708 Allow
> CopletInstanceDataManager to be cloneable.
> An improvement would be to store cached objects in Cocoon Store, the provided
> patch currently uses a simple HashMap to store profiles. Note that the key
> of the object is the URI returned by the source. This is important because
> different values of uri in resolver.resolveURI(uri) could return the same
> source, ie source.getURI() could be the same, so only different objects are
> stored in the Map.
--
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
