nunet-adapter cannot hold protobuf specs for each downstream SNET service
Currently, nunet-adapter service specs include protobuf specs for the downstream snet services that will be deployed on a machine serviced by nunet adapter (i.e. fake_news_score.proto currently). However, this is application specific and cannot be done like this in general case.
The proper way to do this would be to for a nunet-adapter to ask for protobuf specs from the downsteam snet service, receive them via the general- purpose control message and then compile them as protobuf specs, something in this style:
(1) nunet-adapter -> fake_news_score: request for protobuf; (2) fake_news_score -> nunet-adapter: protobuf specs in json on general channel; (3) nunet-adapter: compiles json into protobuf;
I believe the step 3 is achievable via inbuilt json serializers