I agree with Josh. It is very unlikely that we would introduce new keywords
for defining a different kind of service.
On Wednesday, April 26, 2017 at 12:45:29 PM UTC-7, Josh Humphries wrote:
>
> I think the right approach to something like this would be to use the
> existing service definition
I think the right approach to something like this would be to use the
existing service definition support and write a protoc plugin that does the
code gen. To layer on extra things -- for concepts/features that OSGI
supports but that can't be modeled just with proto service definitions --
you
I've been happily using protocol buffers to implement Java <-> Python
interaction using OSGi Remote Services [1,2].
Remote Services is a spec that extends OSGi services to out-of-process
access. A nice thing about the Remote Services spec is that it is
transport-independent...allowing
