StreamingHandlerConn is the server's view of a bidirectional message exchange. Interceptors for streaming RPCs may wrap StreamingHandlerConns. Like the standard library's [http.ResponseWriter], StreamingHandlerConns write response headers to the network with the first call to Send. Any subsequent m
| 93 | // the read side must not be called concurrently with itself, and the write side |
| 94 | // must not be called concurrently with itself. |
| 95 | type StreamingHandlerConn interface { |
| 96 | Spec() Spec |
| 97 | Peer() Peer |
| 98 | |
| 99 | // Receive and RequestHeader form the read side of the stream. They are not |
| 100 | // safe to call concurrently with each other, but may be called concurrently |
| 101 | // with Send, ResponseHeader, and ResponseTrailer. |
| 102 | Receive(any) error |
| 103 | RequestHeader() http.Header |
| 104 | |
| 105 | // Send, ResponseHeader, and ResponseTrailer form the write side of the |
| 106 | // stream. They are not safe to call concurrently with each other, but may |
| 107 | // be called concurrently with Receive and RequestHeader. |
| 108 | Send(any) error |
| 109 | ResponseHeader() http.Header |
| 110 | ResponseTrailer() http.Header |
| 111 | } |
| 112 | |
| 113 | // StreamingClientConn is the client's view of a bidirectional message exchange. |
| 114 | // Interceptors for streaming RPCs may wrap StreamingClientConns. |
nothing calls this directly
no outgoing calls
no test coverage detected