Edward McFarlane

Hi @domino14 thanks for the issue. Currently the mechanisms used by the interceptor don't provide compression. Some exploration work has been done, see this [issue](https://github.com/connectrpc/connect-go/issues/665).

Closing, this needs testcases for error cases, but will pick up at a later time.

Hi Nathan, the vanguard handler will respond in the protocol the client initiated. We follow the protocols defaults for the base settings. So if the protocol is detected as connect...

Passing the `AnyRequest` does feel odd for the streaming handlers. Would your solution in https://github.com/connectrpc/connect-go/pull/851#discussion_r2135765436 solve this case nicely too and we can pass `RequestInfo` to the handler?

@staugaard this has been released in [v1.19.0](https://github.com/connectrpc/connect-go/releases/tag/v1.19.0)

The context code looks correct, however `(stream AskGPTResponse);` requires you implement the full [`Interceptor`](https://pkg.go.dev/connectrpc.com/connect#Interceptor) interface. The current interceptor will only work on unary, it doesn't cover streaming use cases. Would...

@AThilenius thanks for raising the issue, this also caught me by surprise when I first read through the spec and will look at making this more obvious. From the [spec](https://connectrpc.com/docs/protocol/#streaming-rpcs):...

You might find the new conformance tooling useful. It's just been developed to help implementers assert correctness: https://github.com/connectrpc/conformance

Hey @ok32 , this looks like an issue with an optimization. Vanguard won't re-serialize the data if the server "content-type" matches the clients. For the second case this optimization is...

Hi @rendaman0215 I believe this is a server side timeout. The client isn't able to extend the server timeouts.