-
Notifications
You must be signed in to change notification settings - Fork 27
Feature: Add support for Proto3 language #6
Comments
Why is it not possible to write self-describing services in .NET for Protocol Buffers v3? What do you mean by self-describing services? Do you mean code-first with attributes like: |
Have in mind to create a service registration protocol which allows a generic service to register it's FileDescriptorProto (or Set) at run-time, so that the service's metadata can be inspected as well as to provide transcoding from/to JSON, without recompiling the server being registered with. That's what I meant by "self-describing services". The official C# generator from Google will not generate code for proto2, but proto2 is required if one wants to define and process custom options in .NET. So... I am hunting for an alternative. |
I had to read up more about https://developers.google.com/protocol-buffers/docs/proto#options |
Hah. What you missed is that while custom options can be used in proto3, they require proto2 syntax to define (custom options use the |
Requesting simultaneous support for both proto2 and proto3 language syntax, selected via the new
syntax = "[proto2|proto3]";
statement.https://developers.google.com/protocol-buffers/docs/reference/proto3-spec
As possible incentive, the official C# generator for Proto3 does not (and will not) support generating code for the proto2 language, and thus it is not (and will-not-be) possible to write protobuf tooling and self-describing services in .NET.
Perhaps Froto can be used to fill that need.
The text was updated successfully, but these errors were encountered: