1Ordering Status and Reads in the gRPC API
2-----------------------------------------
3
4Rules for implementors:
51. Reads and Writes Must not succeed after Status has been delivered.
62. OK Status is only delivered after all buffered messages are read.
73. Reads May continue to succeed after a failing write.
8   However, once a write fails, all subsequent writes Must fail,
9   and similarly, once a read fails, all subsequent reads Must fail.
104. When an error status is known to the library, if the user asks for status,
11   the library Should discard messages received in the library but not delivered
12   to the user and then deliver the status. If the user does not ask for status
13   but continues reading, the library Should deliver buffered messages before
14   delivering status. The library MAY choose to implement the stricter version
15   where errors cause all buffered messages to be dropped, but this is not a
16   requirement.
17