The design of the capability model has always been with more in mind than OSGi
… Clearly the underlying model allows you to model a lot of things. The only
thing that might be missing is an evaluation function that could grade
solutions. In the OSGi context any solution is ok since there is no cost
difference. However, in many scenarios the cost of different solutions could
vary.
Kind regards,
Peter Kriens
> On 15 Mar 2017, at 11:38, Milen Dyankov <milendyan...@gmail.com> wrote:
>
> Hi all,
>
> Is anyone aware of any attempt to use the requirements&capabilities,
> repositories and resolver specs for anything other than provisioning OSGi
> runtime? It seams to me the specs are generic enough to be used in other
> scenarios.
>
> One example that comes to my mind is provisioning a telecommunication offer.
> Say user purchase "plan A" which requires things like "text messaging",
> "roaming", ... and then resolver finds services with such capabilities which
> on the other hand have their own requirements.
>
> The above is just an example I made up, it's not something I'm really
> interested in. I'm rather looking for any example of usage of those concepts
> outside the scope of their original purpose.
>
> Best,
> Milen
>
>
> --
> http://about.me/milen
> <http://about.me/milen>_______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
