I can read from documentation:
"A client-streaming RPC is also similar to our simple example, except the
client sends a stream of requests to the server instead of a single
request. The server sends back a single response, typically but not
necessarily after it has received all the client’s requests, along with its
status details and optional trailing metadata."
Usually the client does:
- create channel
- creaet stub
- perform the writer = stub->foo(context, reply);
- loop on:
writer->Write(request)
- writer->Done()
- writer->Finish()
- At this point I can read the reply
now my question is how can I read the reply before the loop is over? Some
time the server indeed stops performing the read loop notifying that there
is no need for more requests.
--
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/1b8afe4c-088d-47dd-90e8-7f5cd0949c6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
