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

Update statuscodes.md

Browse Source 
Change wording
pull/16106/head
Yash Tibrewal 7 years ago committed by GitHub
parent 4ec08f7235
commit bcecc177a8
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
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      doc/statuscodes.md

2
doc/statuscodes.md
Unescape View File

@ -49,4 +49,4 @@ The following status codes are never generated by the library:
- OUT_OF_RANGE
- DATA_LOSS
The decision to retry RPCs at the application level depends on the application and the type of error. There is no single guidance that will work for all.
Applications that may wish to retry failed RPCs must decide which status codes on which to retry. As shown in the table above, the gRPC library can generate the same status code for different cases. Server applications can also return those same status codes. Therefore, there is no fixed list of status codes on which it is appropriate to retry in all applications. As a result, individual applications must make their own determination as to which status codes should cause an RPC to be retried.

Write Preview
Loading…
Cancel
Save