"...To make any progress on anything being pluggable, one approach is to provide a convention for doing the plugging...."
So we're basically saying there's no runtime DI framework for Scala out the shelf and we need to come up with one ? It's fine if we do, but it would be great to list our assumptions on the things we're interested to support. i.e. do we want to factor in versioning with semantics for when 2 module versions are compatible, dependency chains, composition, etc. We also need to agree on what gets packaged by default in the docker containers for the controller and invoker, as this decision can make it easier or harder for users to switch implementations. Other than that, I +1 Tyson's idea which looks simple, easy to understand, and if it helps us initialize components dynamically, at runtime, it would be great to proceed with it sooner than later. There's also some thoughts and implementations into the Play Framework [1], but I'm not sure how adaptable those are for OW. dragos [1] - https://www.playframework.com/documentation/2.5.x/ScalaDependencyInjection ________________________________ From: Rodric Rabbah <[email protected]> Sent: Friday, June 9, 2017 5:45:52 PM To: [email protected] Subject: Re: Pluggable components in OpenWhisk Thanks for taking a shot at this! - at first glance it looks like this may be a good fit. I'll go through it more slowly to provide more informed feedback. -r
