Ok, it seems like the situation is even worse, and this is really frustrating.
Using a Go GRPC server (didn't test anything else), I cannot even get `Write()` to fail even when the remote server does not implement the method I'm calling! I'm sending a message every 5 seconds to a GRPC server that doesn't implement the method/service, and I keep getting `true` return values (code is running for >5m now). Now, I can call `Finish` at any time and will then in fact get the "unknown service xyz" in the status response, but for that I'd have to close the stream - doesn't work with my use case.
I somehow can't believe that this is really the state of affairs with the GRPC C++ API, but I've looked through most of the API and don't see a solution. I apologize if that sounds harsh, but if it is impossible to make a client-side streaming RPC call without knowing whether all the data gets effectively sent to /dev/null before closing this stream (regardless of session length), it seems that client-side streaming is effectively unusable from C++..? (This very use case works absolutely fine in Golang)