Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read bundle meta-data without loading the bundle's code into the process. #2

Closed
6 tasks done
jeffdiclemente opened this issue Aug 4, 2015 · 1 comment
Closed
6 tasks done
Assignees
Milestone

Comments

@jeffdiclemente
Copy link
Owner

We want to be able to read a bundle's meta-data without loading it into the process. Doing this provides better performance when dealing with many bundles.

There are a few related technical issues to doing this which need to be solved:

  • Removal of most, if not all, static globals within CppMicroServices.
  • "Framework" and "Framework Factory" classes as a single entry point for clients to initialize CppMicroServices.
  • A minimal lifecycle for bundles, consisting solely of "install", "start" and "stop".
  • Bundles are installed first and then loaded into the process only on bundle activation.
  • Transition to declaring the bundle name in the bundle's manifest file.
  • Auto-loading needs to be either factored out into a service or modified to allow auto-installing of bundles.
@jeffdiclemente jeffdiclemente self-assigned this Aug 4, 2015
@jeffdiclemente jeffdiclemente modified the milestone: 3.0 Aug 4, 2015
jeffdiclemente added a commit that referenced this issue Aug 24, 2015
Fixed known bugs
Addressed "TODO" items
Updated documentation

Closes #2

Signed-off-by: The MathWorks, Inc. Roy.Lurie@mathworks.com
jeffdiclemente added a commit that referenced this issue Aug 25, 2015
This includes a few other changes required to be able to remove static globals:

- "Framework" and "Framework Factory" classes as a single entry point for clients to initialize CppMicroServices.
- A minimal lifecycle for bundles, consisting solely of "install", "start" and "stop".
- Bundles are installed first and then loaded into the process only on bundle activation.
- Transition to declaring the bundle name in the bundle's manifest file.
- Auto-loading needs to be either factored out into a service or modified to allow auto-installing of bundles.

Closes #2

Signed-off-by: The MathWorks, Inc. Roy.Lurie@mathworks.com
jeffdiclemente added a commit that referenced this issue Aug 25, 2015
This includes a few other changes required to be able to remove static globals:

- "Framework" and "Framework Factory" classes as a single entry point for clients to initialize CppMicroServices.
- A minimal lifecycle for bundles, consisting solely of "install", "start", "stop" and "uninstall".
- Bundles are installed first and then loaded into the process only on bundle activation.
- Transition to declaring the bundle name in the bundle's manifest file.
- Auto-loading needs to be either factored out into a service or modified to allow auto-installing of bundles.

Closes #2

Signed-off-by: The MathWorks, Inc. Roy.Lurie@mathworks.com
@jeffdiclemente
Copy link
Owner Author

Merged pull request #31 from saschazelzer/development. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant