Doug Fawley

Sure, that would be helpful, thanks!

@ejona86 we talked about this awhile ago - does Java have a way to distinguish client-produced errors from server errors or connection errors?

FWIW, retries and hedging are coming to gRPC-Go natively in a month or two. [Relevant gRFC](https://github.com/grpc/proposal/blob/master/A6-client-retries.md#retry-and-hedging-statistics). Regarding the initial issue, we have since created the [bufconn](https://godoc.org/google.golang.org/grpc/test/bufconn) package to at least...

@Random-Liu, > Any updates on this? We were literally talking about this yesterday, so we haven't forgotten about it. However, it's still not at the top of our priority list....

> The library avoids serialization/de-serialization, but it does copy. Aha, I see now. So you do a `proto.Clone()` for proto messages, and a best-effort shallow copy otherwise ([ref](https://github.com/fullstorydev/grpchan/blob/b5fef0eb7ef0d002150913f0f4038852d185ddad/internal/misc.go#L17)). FWIW, it...

FWIW, in the next quarter, I plan to redesign the interface/abstractions between the `grpc` & `transport` packages to make it possible for custom transports to be implemented.

@Daniel-B-Smith yes, I believe it would unblock any efforts to implement that (with the caveat that the core grpc-go team is not committed to implementing it). I'll have an update...

I am far enough along with a prototype that I'm ready to share some details on this effort. Please feel free to review and provide feedback. First, some of my...

An important detail I left out is how to inject these custom transports. Server-side, the story is simple: instead of giving grpc a `net.Conn`-based `Listener`, you would pass it a...

@annismckenzie I'm targeting something in the next month or so. I am taking a couple weeks off soon, but hopefully I can wrap things up pretty quickly when I return...