*Main Question:* Is there any way to check if an internal error was set by the server without making a new Write operation in a single direction Client->Server streaming scenario, and without calling Finish.
Currently we are using a client and server with the gRPC C++ client streaming to a server. Some messages result in the connections being failed with a status. With the completion queue API in C++, this is only detectable as soon as the next Write operation is detected, since the `ok` booleans attached to the completion queue tasks are simply denoting whether the write "made it" to flow-control. In our use case, there can be varying period of time where there are no writes made, but we still want to detect the internal failure at the server end as soon as possible. In this PR here https://github.com/grpc/grpc/pull/19868, it seems like it was added that the transport object would set the "stream_write_closed" flag in the `send_message` operation struct to true, but this seems related to catching the error on the next operation, so it doesn't seem related. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/db81eb79-8c43-47d5-8014-a5afbdae5c23n%40googlegroups.com.
