|
|
|
@ -1135,7 +1135,7 @@ responses, it closes with OK. |
|
|
|
|
### Echo Status |
|
|
|
|
[Echo Status]: #echo-status |
|
|
|
|
When the client sends a response_status in the request payload, the server closes |
|
|
|
|
the stream with the status code and messsage contained within said response_status. |
|
|
|
|
the stream with the status code and message contained within said response_status. |
|
|
|
|
The server will not process any further messages on the stream sent by the client. |
|
|
|
|
This can be used by clients to verify correct handling of different status codes and |
|
|
|
|
associated status messages end-to-end. |
|
|
|
@ -1152,7 +1152,7 @@ key and the corresponding value back to the client as trailing metadata. |
|
|
|
|
[Observe ResponseParameters.interval_us]: #observe-responseparametersinterval_us |
|
|
|
|
|
|
|
|
|
In StreamingOutputCall and FullDuplexCall, server delays sending a |
|
|
|
|
StreamingOutputCallResponse by the ResponseParameters's `interval_us` for that |
|
|
|
|
StreamingOutputCallResponse by the ResponseParameters' `interval_us` for that |
|
|
|
|
particular response, relative to the last response sent. That is, `interval_us` |
|
|
|
|
acts like a sleep *before* sending the response and accumulates from one |
|
|
|
|
response to the next. |
|
|
|
|