Hello,

I found recently that grpc-go was working on an xds implementation for service discovery, which is great.

Using current HEAD, I tried to get both resolver and balancer working. I managed to get something more or less working for resolver by reversing code & tests code on Gist but as for balancer, I didn't.

I unders

We should expose something akin to warp::service that allows the Router type to turn into a Service implementation so that it can be combined with more custom implementations.

I have a function that is a normal request with streaming response, and these are my questions/confusions:

Should I be calling GRPC.Stub.recv on the stream multiple times? It feels like I should.

The documentation mentions the end_stream function, then it says this:

The stream will be in half_closed state after this is called.

So presumably there is a way to get the stream

If you use gogoproto's custom types (https://github.com/gogo/protobuf/blob/master/custom_types.md) e.g.:

import "myorg/customtypes/time/time.proto";
...
message Example { 
    time.CustomTime created = 3 [(gogoproto.customtype) = "myorg/customtypes/time.CustomTime"];
}

mwitkow validators generates a file with unused imports:

19:33:28  generated/xxxx.pb.go:17:2: importe

At the moment this plugin generates two files for each processed *.proto file with names:

• <protofile>_transformer.go
• options.go

In this case it's hard to say were these files auto-generated or weren't by its names.

Use additional file extension for auto-generated files: *.pb.st.go, as a result files should be named as :

• <protofile>.pb.st.go
• options.pb.st.go