Consistently applying updates to compositions of distributed OSGi modules
Proceedings of the 1st International Workshop on Hot Topics in Software Upgrades, HotSWUp'08, Page: 1-5
2008
- 5Citations
- 16Captures
Metric Options: CountsSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Conference Paper Description
Updating software at runtime is a challenge that covers various aspects of software design and runtime systems. The OSGi Alliance has proposed and standardized a runtime system for composing Java applications out of modules, the OSGi Framework. The possibility to update modules at runtime and thereby dynamically change the application has been an intrinsic design decision of the framework architecture. With recent approaches to extend the OSGi model from single Java virtual machines to distributed systems, however, updates no longer only affect a single machine in the system. The specifications of OSGi and the upcoming proposals for distributed OSGi services do not answer the question how to consistently apply updates in such environments. In this paper, we explore a solution based on our R-OSGi system. We show how to extend the existing (local) OSGi update mechanism to consistently apply updates to multiple nodes of a distributed OSGi application. Copyright © 2008 ACM.
Bibliographic Details
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know