You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2011/09/20 21:26:08 UTC
[jira] [Created] (FELIX-3125) [Framework] Use single file per
bundle in bundle cache by default
[Framework] Use single file per bundle in bundle cache by default
-----------------------------------------------------------------
Key: FELIX-3125
URL: https://issues.apache.org/jira/browse/FELIX-3125
Project: Felix
Issue Type: Improvement
Components: Framework
Affects Versions: framework-3.2.2
Reporter: Richard S. Hall
Assignee: Richard S. Hall
Priority: Minor
Fix For: framework-4.0.0
FELIX-2654 modified the bundle cache so it would use a single file per bundle to store bundle-related state (e.g., location, persisted state, etc.). The main reason was to reduce the amount of I/O performed during framework startup when you have lots of already cached bundles. This feature was disabled by default, since it didn't seem proper to introduce it in a micro release when it would result in bundle caches not being backward compatible with previous micro releases of 3.0.x.
WIth the coming framework 4.0 release, we should switch this to be the default. Which means that new bundle caches created on 4.0 will not work with older releases. However, bundle caches created with older releases will be seamlessly converted by 4.0. Older caches will be converted non-destructively, so it is possible to go back, but if changes are made while running 4.0 on an older cache, then it is possible that they will get out of sync and will potentially no longer be backward compatible.
For the foreseeable future, we can keep the felix.cache.singlebundlefile property which allows you to revert to the old behavior if you so choose. At some point in the future, though, it would be desirable to eliminate this property too and only support the new cache format.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (FELIX-3125) [Framework] Use single file per bundle
in bundle cache by default
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall closed FELIX-3125.
----------------------------------
Resolution: Fixed
I committed a patch to change the default; closing this issue.
> [Framework] Use single file per bundle in bundle cache by default
> -----------------------------------------------------------------
>
> Key: FELIX-3125
> URL: https://issues.apache.org/jira/browse/FELIX-3125
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Affects Versions: framework-3.2.2
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: framework-4.0.0
>
>
> FELIX-2654 modified the bundle cache so it would use a single file per bundle to store bundle-related state (e.g., location, persisted state, etc.). The main reason was to reduce the amount of I/O performed during framework startup when you have lots of already cached bundles. This feature was disabled by default, since it didn't seem proper to introduce it in a micro release when it would result in bundle caches not being backward compatible with previous micro releases of 3.0.x.
> WIth the coming framework 4.0 release, we should switch this to be the default. Which means that new bundle caches created on 4.0 will not work with older releases. However, bundle caches created with older releases will be seamlessly converted by 4.0. Older caches will be converted non-destructively, so it is possible to go back, but if changes are made while running 4.0 on an older cache, then it is possible that they will get out of sync and will potentially no longer be backward compatible.
> For the foreseeable future, we can keep the felix.cache.singlebundlefile property which allows you to revert to the old behavior if you so choose. At some point in the future, though, it would be desirable to eliminate this property too and only support the new cache format.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira