Whoops, hit reply to early. Even when using the stream to send keep-alives at regular intervals (which I do not believe should be done at the application level), the fact that a call to `Write` might return true just after writing to the buffer might make even this approach unreliable.
Any help would be very much appreciated. Note: I'm using the sync API, but I didn't find anything in the async API either. On Wednesday, September 19, 2018 at 4:55:40 PM UTC-7, [email protected] wrote: > > Hi, > > I'm having trouble using the GRPC C++ API for a unidirectional stream RPC > (client streaming, client is written in C++, server in Go). > > Unless I'm missing something, it seems that the only way to find out if > the remote (receiving) end of the stream aborted the GRPC call is by > actually calling Write(). For streaming connections that send data only > infrequently (but which need to be streaming nonetheless, due to > statefulness of a single "call" and ordering guarantees), this seems very > unsatisfying. Even when using the stream to send keep-alives at regular > intervals (which I do not believe should be done at the application level), > the fact that a call to `Write > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/688fc590-c8a4-4a39-9704-28b5e9b9325d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
