You can just create an instance like this:
class TestClientBidiReactor : public ClientBidiReactor<TestRequest,
TestResponse> {
public:
explicit TestClientBidiReactor(Stub* stub, ClientContext& context, ...) {
...}
There is StartRead and StartWrite
StartCall will activate the call (so use after Read and Write)
You can implement OnReadDone, OnWriteDone, and/or OnDone to achieve the
callback behaviour you need.
ClientCallBackReadWrite you can also create; just watch out that the
streaming objects are not actually implemented in the public API. A
reactor is usually used!
On Wednesday, November 4, 2020 at 1:49:30 PM UTC-8 christo...@gmail.com
wrote:
> I see these classes mentioned in the grpc "docs", but I do not see how to
> get yourself an instance of them when making an RPC call. How do you get
> one? Can I indeed be called back when reads or writes complete? That would
> suit me much better than the ClientReaderWriter interface.
--
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 grpc-io+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/2fba8ae6-567f-473a-8276-6bbed9138234n%40googlegroups.com.
