Hi, On Thu, Apr 24, 2014 at 4:48 AM, Chetan Mehrotra <[email protected]> wrote: > Currently we are having following interfaces as part of exported > packages [2]. Looking at the list I believe most are of ProviderType > i.e. provided by Oak and not required by Oak API users.
Not really. Almost all of the interfaces we expose are various kinds of extension points that can be used for plugging in custom functionality. The fact that we provide a number of default implementations doesn't exclude anyone from adding their own components. I think only the Oak API itself is something for which custom implementations wouldn't be expected. BR, Jukka Zitting
