You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
…merge/master/by_topic/aquilon_203_current_default_dns_domain_assumed_valid to master
* commit '76048891d6ca66486032b9391385628ecc974a8f':
Change to same DNS domain for buidlings optimised
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.
The text was updated successfully, but these errors were encountered: