Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Major refactoring for allowing to drop the one-to-one plugin and plugin context relationship. We eventually want to allow multiple instances of one plugin (python plugin comes to mind). When we use an alist for storing the plugin context which has a pointer to the actual plugin that the context is linked to we can easily use the actual callback we need to call in the plugin with the active context. As we are no longer walking the shared plugin alist we also don't need to always use the foreach_alist_index to be sure we don't run into problems with multi threading. Some state is captured in the shared plugin data which is used by multiple threads in the filed. This is probably not to smart as it means that the state is shared between multiple threads and so multiple backup jobs what is not something you want. As this is mostly core code and probably not used by any important plugin in the wild it might for now not be a big problem but it may become a problem if we implement some more filed plugins. Added the bDirEventNewPluginOptions event which will allow the dir to implement the loading of multiple instances of the same plugin each with its private context. Added the bsdEventNewPluginOptions event which will allow the storage daemon to implement the loading of multiple instances of the same plugin each with its private context.
- Loading branch information
Marco van Wieringen
committed
Feb 17, 2015
1 parent
e869aba
commit f26034d
Showing
21 changed files
with
683 additions
and
342 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.