You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jeanne Waldman (JIRA)" <de...@myfaces.apache.org> on 2011/03/02 19:22:37 UTC

[jira] Updated: (TRINIDAD-2025) move _styleNodeToStyleMap to FileSystemStyleCache to take advantage of same entires on the higher, browser or version or platform layer

     [ https://issues.apache.org/jira/browse/TRINIDAD-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeanne Waldman updated TRINIDAD-2025:
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-2
           Status: Resolved  (was: Patch Available)

> move _styleNodeToStyleMap to FileSystemStyleCache to take advantage of same entires on the higher, browser or version or platform layer
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-2025
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2025
>             Project: MyFaces Trinidad
>          Issue Type: Improvement
>          Components: Skinning
>    Affects Versions: 2.0.0-beta-1
>            Reporter: Jeanne Waldman
>            Assignee: Jeanne Waldman
>             Fix For: 2.0.0-beta-2
>
>         Attachments: UnmodifiableStyleAndSelectorMemoryFixes.patch
>
>
> We still have too many CSSStyle objects after we implemented #1 and #2 from TRINIDAD-1782.
> Implement #3 from TRINIDAD-1782 to reduce the number of Style objects. That is, move the _styleNodeToStyleMap out of StylesImpl up to FileSystemStyleCache.
> In our Rich Client app, one FileSystemStyleCache$StylesImpl was using around 2.5M.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira