GRPC C++
1.66.0
|
An interface allowing implementors to process and filter event tags. More...
#include <completion_queue_tag.h>
Public Member Functions | |
virtual | ~CompletionQueueTag () |
virtual bool | FinalizeResult (void **tag, bool *status)=0 |
FinalizeResult must be called before informing user code that the operation bound to the underlying core completion queue tag has completed. More... | |
An interface allowing implementors to process and filter event tags.
|
inlinevirtual |
|
pure virtual |
FinalizeResult must be called before informing user code that the operation bound to the underlying core completion queue tag has completed.
In practice, this means:
This is the method that translates from core-side tag/status to C++ API-observable tag/status.
The return value is the status of the operation (returning status is the general behavior of this function). If this function returns false, the tag is dropped and not returned from the completion queue: this concept is for events that are observed at core but not requested by the user application (e.g., server shutdown, for server unimplemented method responses, or for cases where a server-side RPC doesn't have a completion notification registered using AsyncNotifyWhenDone)
Implemented in grpc::ServerInterface::GenericAsyncRequest, grpc::ServerInterface::PayloadAsyncRequest< Message >, grpc::ServerInterface::RegisteredAsyncRequest, and grpc::ServerInterface::BaseAsyncRequest.