gRPC: Role of the ClientAsyncStreamingInterface.Finish() and the CompleitionQueue
up vote
0
down vote
favorite
I'm trying to understand the greeter_async_client.cc from the helloworld example of the gRPC docs.
With respect to line 76:
rpc->Finish(&reply, &status, (void*)1);
The api reference mentions that the ClientAsyncStreamingInterface::Finish()
function will return if:
This function will return when either:
- all incoming messages have been read and the server has returned a status.
- the server has returned a non-OK status.
- the call failed for some reason and the library generated a status.
Does this mean that Finish()
is blocking? And if it is, then what is the role of the CompletionQueue
. Can't we just read the response once the Finish()
call returns?
grpc
add a comment |
up vote
0
down vote
favorite
I'm trying to understand the greeter_async_client.cc from the helloworld example of the gRPC docs.
With respect to line 76:
rpc->Finish(&reply, &status, (void*)1);
The api reference mentions that the ClientAsyncStreamingInterface::Finish()
function will return if:
This function will return when either:
- all incoming messages have been read and the server has returned a status.
- the server has returned a non-OK status.
- the call failed for some reason and the library generated a status.
Does this mean that Finish()
is blocking? And if it is, then what is the role of the CompletionQueue
. Can't we just read the response once the Finish()
call returns?
grpc
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to understand the greeter_async_client.cc from the helloworld example of the gRPC docs.
With respect to line 76:
rpc->Finish(&reply, &status, (void*)1);
The api reference mentions that the ClientAsyncStreamingInterface::Finish()
function will return if:
This function will return when either:
- all incoming messages have been read and the server has returned a status.
- the server has returned a non-OK status.
- the call failed for some reason and the library generated a status.
Does this mean that Finish()
is blocking? And if it is, then what is the role of the CompletionQueue
. Can't we just read the response once the Finish()
call returns?
grpc
I'm trying to understand the greeter_async_client.cc from the helloworld example of the gRPC docs.
With respect to line 76:
rpc->Finish(&reply, &status, (void*)1);
The api reference mentions that the ClientAsyncStreamingInterface::Finish()
function will return if:
This function will return when either:
- all incoming messages have been read and the server has returned a status.
- the server has returned a non-OK status.
- the call failed for some reason and the library generated a status.
Does this mean that Finish()
is blocking? And if it is, then what is the role of the CompletionQueue
. Can't we just read the response once the Finish()
call returns?
grpc
grpc
asked Nov 7 at 20:30
ConfusedSoul
33
33
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53197348%2fgrpc-role-of-the-clientasyncstreaminginterface-finish-and-the-compleitionqueu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown