Hi, "ich bin" wrote: >>> My question is that is it possible to support strong migration of OSGi >>> bundles?
There is a nice definition in http://citeseer.comp.nus.edu.sg/676839.html The authors come to the conclusion that strong migration is impossible in the JVM. I find their arguments very convincing: strong migration means the program can be unaware of being migrated and involves sending stack, instruction pointer and registers along with the code while weak migration can be triggered by the program itself and only sends the code itself. As you already mentioned, weak migration does not transport more state of the program than is being actively transmitted by the program. A complication is that in a running OSGi system it may not be enough to just transmit one bundle's state since that state might depend on other bundles as well. This leads me to believe that weak migration is quite feasible in an OSGi platform (just grab the bundle's bytes, e.g. using the Bundle-Location: header, and send them elsewhere) while strong migration is probably to hard to be useful. Harald _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
