Chiebot-Mirror
/
grpc
mirror of https://github.com/grpc/grpc.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #20602 from zhiliangxu/patch-1

Browse Source 
Fix a typo in transport_explainer.md
pull/20623/head
Vijay Pai 5 years ago committed by GitHub
parent 6e4d2e86dc 4030b49f71
commit 6a4fe42f01
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      doc/core/transport_explainer.md

2
doc/core/transport_explainer.md
Unescape View File

@ -100,7 +100,7 @@ There are other possible sample timelines. For example, for client-side streamin
through an `AsyncNotifyWhenDone` API in C++ through an `AsyncNotifyWhenDone` API in C++
1. Client: send\_initial\_metadata, recv\_message, recv\_trailing\_metadata 1. Client: send\_initial\_metadata, recv\_message, recv\_trailing\_metadata
- At API-level, that's a client invoking a client-side streaming call. The - At API-level, that's a client invoking a client-side streaming call. The
send\_initial\_metadata is the call invocation, the recv\_message colects send\_initial\_metadata is the call invocation, the recv\_message collects
the final response from the server, and the recv\_trailing\_metadata gets the final response from the server, and the recv\_trailing\_metadata gets
the `grpc::Status` value that will be returned from the call the `grpc::Status` value that will be returned from the call
1. Client: send\_message / Server: recv\_message 1. Client: send\_message / Server: recv\_message

Write Preview
Loading…
Cancel
Save