-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request grpc#10005 from ctiller/status_ordering
Document status ordering rules
- Loading branch information
Showing
2 changed files
with
19 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
Ordering Status and Reads in the gRPC API | ||
----------------------------------------- | ||
|
||
Rules for implementors: | ||
1. Reads and Writes Must not succeed after Status has been delivered. | ||
2. OK Status is only delivered after all buffered messages are read. | ||
3. Reads May continue to succeed after a failing write. | ||
However, once a write fails, all subsequent writes Must fail, | ||
and similarly, once a read fails, all subsequent reads Must fail. | ||
4. When an error status is known to the library, if the user asks for status, | ||
the library Should discard messages received in the library but not delivered | ||
to the user and then deliver the status. If the user does not ask for status | ||
but continues reading, the library Should deliver buffered messages before | ||
delivering status. The library MAY choose to implement the stricter version | ||
where errors cause all buffered messages to be dropped, but this is not a | ||
requirement. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters