You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Sahoo (JIRA)" <ji...@apache.org> on 2009/02/14 02:44:59 UTC
[jira] Updated: (FELIX-939) Optimize File Install
[ https://issues.apache.org/jira/browse/FELIX-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sahoo updated FELIX-939:
------------------------
Attachment: FELIX-937-938-939.patch
PFA a patch for following File Install bundle issues;
https://issues.apache.org/jira/browse/FELIX-937
https://issues.apache.org/jira/browse/FELIX-938
https://issues.apache.org/jira/browse/FELIX-939
> Optimize File Install
> ---------------------
>
> Key: FELIX-939
> URL: https://issues.apache.org/jira/browse/FELIX-939
> Project: Felix
> Issue Type: Improvement
> Environment: generic
> Reporter: Sahoo
> Attachments: FELIX-937-938-939.patch
>
>
> File Install has a dedicated thread for every directory. That thread wakes up periodically and then does the following:
> 1. Iterates over all the bundles by calling context.getBundles
> 2. Finds out all bundles which belong to watchedDir. It starts them.
> 3. Finds if there is any new jar file in the watchedDir. It installs them.
> 4. Finds out if any jar has been deleted from watcheDir. It uninstalls corresponding bundles.
> 5. Finds out if any jar has been modified. It updates the corresponding bundles.
> I think there is some scope for optimization here. Especially step #2 seems redundant if there has been change in the file system. More over, if out of all the bundles in the system, only a few belong to watchedDir, then the current implementation performs poorly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.