Hi Klaus, I am also interested in this subject and posted something before deleting it after seeing your thread here. Funny how crafting a good post sometimes leads to answering one's own questions.
My justification along your inquiry is the ability for the nodes to resolve the transitive closure of jars they need against a production repository. So the cluster node loader would understand from the roles it's started with what root functionality it needs to present, loading the transitives it needs from a read-only repository. This is really quite tractable with OSGi and Akka has very good support in this regard. In turn, the justification for OSGi is so old versions of code can be run concurrently with new versions. This is important in a heterogeneous environment with a large number of clients that can't be upgraded simultaneously. Rather than forcing clients to upgrade, they can provide their version as a header and be mapped to the correct legacy version of the API. Newer clients can run newer API versions and they can all coexist without burying the code base in conditionals created to maintain backwards compatibility. Of course certain legacy version ranges might be consolidated on branches. Most importantly, new versions are not saddled with these costs and can innovate freely with little or no attention paid to backwards compatibility. There are limits to this, of course. But it's a far better situation than not having the option at all. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
