sanjaypujare

I just realized there is another (simpler) way too: you can modify the request proto to make the actual request data optional and in case of a cache hit in...

Looks like we can close this? Let us know if you have more questions/comments

These bindings are required when xds is used even if certain classes are not used in certain situations (e.g. server side config protos when the application is just a client...

> ... might make sense to split the grpc-xds package even further. Could you elaborate on the split? Split along which lines?

> CC @sanjaypujare, since we've talked about TLS+plaintext on a single port before Yes. One thing to mention is that for xDS managed servers this support is there (but not...

> ... > Not quite what is being discussed here. Here we want to support a client that may be TLS or plaintext. That requires sniffing the initial bytes. The...

> All I want is to get the channel from the server By channel you mean an Http2Connection that is created for each incoming connection from a client? > and...

It looks like the PPV2 info you want is just the local and remote addresses on a connection. That is available already in gRPC on the `ServerCall` object as shown...

@madanrajhari let me know if the above has addressed your question. If not I would like to know what specifically you need that would require a CustomHandler.

Since this is answered on SO, this can be closed?