Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for protobuf v3 to make it easier to work with JSON #71

Open
ned21 opened this issue Oct 25, 2017 · 0 comments
Open

Support for protobuf v3 to make it easier to work with JSON #71

ned21 opened this issue Oct 25, 2017 · 0 comments

Comments

@ned21
Copy link
Contributor

ned21 commented Oct 25, 2017

The strategic long-term solution is to renovate the protobuf formatter based on version 3 of the protobuf specification, which does include a canonical translation from protobuf to JSON. Ideally, the broker would only produce protobuf 3 data; all translation to human-readable format would happen on the client side.

@jrha has volunteered an intern to do the coding work if someone can provide a design and reference implementation of one command.

@ned21 ned21 mentioned this issue Oct 25, 2017
ned21 pushed a commit to ned21/aquilon that referenced this issue Mar 4, 2020
…merge/master/by_topic/aquilon_203_current_default_dns_domain_assumed_valid to master

* commit '76048891d6ca66486032b9391385628ecc974a8f':
  Change to same DNS domain for buidlings optimised
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant