You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2012/07/10 11:50:35 UTC

[jira] [Updated] (OAK-176) Reduce CoreValueFactoryImpl footprint

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

Jukka Zitting updated OAK-176:
------------------------------

    Fix Version/s: 0.4
    
> Reduce CoreValueFactoryImpl footprint
> -------------------------------------
>
>                 Key: OAK-176
>                 URL: https://issues.apache.org/jira/browse/OAK-176
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.4
>
>
> KernelNodeState and associated classes currently need to carry around a ValueFactory instance, when they could just as well simply instantiate one whenever needed based on the already available MicroKernel reference. Doing so would reduce the amount of objects we need to keep around and thus simplify a few code paths. The CoreValueFactoryImpl has no state of it's own, so there's no inherent need why we'd need just a single instance of it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira