One of the greatest benefits of OSGi is its firewall-esque encapsulation of implementation details. The only traffic that gets in or out is the traffic that you explicitly specify, otherwise all bets are off. The aspiring polyglot can bring in the right tool for the right job by hiding it behind OSGi services as an “implementation detail,” provided that only Java language types are exported. The talk will look at the pros and cons of this approach, experiment with Groovy, Clojure, and Scala in an OSGI container, and also look at the “gotchas” involved along the way.
It was a good presentation and I'll be doing more research into OSGi to see how I can use it on my current project.
No comments:
Post a Comment