Skip to content
Snippets Groups Projects
Commit befd64ea authored by Nathaniel Manista's avatar Nathaniel Manista
Browse files

Merge pull request #572 from ctiller/dox7

Clarify completion queue laws
parents d50bf4d9 8ac56c96
No related branches found
No related tags found
No related merge requests found
......@@ -394,7 +394,12 @@ grpc_event *grpc_completion_queue_pluck(grpc_completion_queue *cq, void *tag,
void grpc_event_finish(grpc_event *event);
/* Begin destruction of a completion queue. Once all possible events are
drained it's safe to call grpc_completion_queue_destroy. */
drained then grpc_completion_queue_next will start to produce
GRPC_QUEUE_SHUTDOWN events only. At that point it's safe to call
grpc_completion_queue_destroy.
After calling this function applications should ensure that no
NEW work is added to be published on this completion queue. */
void grpc_completion_queue_shutdown(grpc_completion_queue *cq);
/* Destroy a completion queue. The caller must ensure that the queue is
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment