Joshua Humphries

@alapativ2, FYI, versions prior to [1.2.0](https://github.com/fullstorydev/grpcui/releases/tag/v1.2.0) actually used an HTML layout to display the response instead of the text area with the JSON contents. But it turns out that RPC...

@PavelA85, metadata keys in gRPC (and in HTTP headers) are case-insensitive. In HTTP/2, they are always transmitted in lower-case. This lower-casing is done because the keys in a `metadata.MD` map...

For the first one (request should have no body), that indeed can and should be fixed. The second one is less clear thanks to the gRPC docs/specs for error-handling. If...

@evanmoran, the first line of that Reddit post is the key: > Going to need both gRPC (backend) and REST (frontend) for a new project. If you need to support...

The handler closes the stream by returning. If you need to close it with an RPC error code, you simply have the handler return a non-nil error. Any concurrent calls...

FWIW, this library is built on `net/http` and the RPC handler routine is an `http.Handler`. The `net/http` package does not provide any way to terminate an in-progress HTTP operation other...

> I don't know if there is some hidden "always receive client messages in another goroutine" connect best practice, but intuitively there shouldn't be I guess. It totally depends on...

> the root cause is clearly on jhump/protoreflect @baganokodo2022, I don't agree. The output in your examples is perfectly valid Protobuf source. Message literals in custom option values are allowed...

FWIW, I think there is still a bug in Confluent that needs fixing: it should _not_ be complaining about the use of angle brackets as that **is** allowed in protobuf...

@mattdowdell, response validation has come up more than once before, so we'll keep this on the backlog. If/when we add such an option, it will be simpler -- just a...