Hi Justin, On Wed, Jun 27, 2018 at 9:16 PM Justin Edelson <[email protected]> wrote: > ...Looking at this specific case, I'm now thinking that the implementation of > a servlet here is non-idiomatic. It would be better (at least from my > perspective), if this was all handled via ResourceProvider...
> ...@Bertrand - is there a reason you went with a single servlet implementation > vs. having each capability source be its own resource?.. I did that just because it was the first idea that came to mind, but I see your point! In the meantime, for my application I'm thinking about a different way of expressing capabilities, by publishing links to services instead of values (like Capabilities) that tell if those services are available - that's a more Resource-based approach and I think it resonates with what you're saying here. I'm waiting for feedback from my colleagues and will come back to this once I have it. -Bertrand
