zipkin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [incubator-zipkin-api] dio opened a new issue #74: Consider providing .proto for all API specs
Date Fri, 10 May 2019 08:58:58 GMT
dio opened a new issue #74: Consider providing .proto for all API specs 
URL: https://github.com/apache/incubator-zipkin-api/issues/74
 
 
   Currently, zipkin APIs are represented as:
   
   1. v1, http-json, through https://github.com/apache/incubator-zipkin-api/blob/master/zipkin-api.yaml
   2. v2, http-json, through https://github.com/apache/incubator-zipkin-api/blob/master/zipkin2-api.yaml
and also we have http-proto with messages defined in https://github.com/apache/incubator-zipkin-api/blob/master/zipkin.proto
   
   To make it seamless and take advantage of protobuf tooling when making zipkin clients,
I think it is a good idea to have .proto for all available API specs (including v1 and v2
http json). E.g. in Envoy we can purely use protobuf helps without a detour on using json
lib like rapidjson.
   
   We can consider bringing: https://github.com/nytimes/openapi2proto to generate .proto from
openapi spec.
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message