Joshua Humphries

@frozenbonito, I apologize for the confusion. But the doc states that they are always sent as **HTTP headers**, not as RPC header metadata. So if you were using middleware for...

@ravikanthdba, the `requestData` argument is what the `InvokeRPC` function uses to retrieve the actual message data to send. So you would provide a function that populates the given message with...

That error message looks like it may be related to the HTTP/2-related configuration of your nginx server, and not necessarily related to the use of a server-streaming RPC with nginx....

These lines in the config look suspicious: ``` proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; ``` Do you also have web socket endpoints? IIRC, most browsers and most servers do not...

@solarhell, if you also need to use web sockets, I'd recommend using plain HTTP 1.1 in the nginx config and not trying to use HTTP/2 at all. That should work...

@tahadostifam, thank you for offering. I see you already have a PR over inhttps://github.com/connectrpc/connectrpc.com. I'll add comments over there.

@oronbz, I assume you are already using another plugin with `protoc` in order to generate the base Swift code. So that would look roughly like so: ``` protoc --swift_out=. my.proto...

FWIW, this all a standard part of using plugins with `protoc`. Sadly, the Protobuf developer site (protobuf.dev) doesn't seem to have this information. But if you search for "how to...

Out of curiosity, what will this be used for? Also, I see this commit showed up over in #468. Should this PR still be marked as a draft?

Should this PR be closed now?