aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorGravatar Jan Tattermusch <jtattermusch@users.noreply.github.com>2015-06-22 12:25:55 -0700
committerGravatar Jan Tattermusch <jtattermusch@users.noreply.github.com>2015-06-22 12:25:55 -0700
commitaadc13adc0dd9e7f81c20680dc23ec09fd1b91c9 (patch)
tree04bc7a545599281e8a0607e457d87ba05310460a
parentc878e2a32f48056e7ab26802c228c853f72d3743 (diff)
clarify grpc_call_start_batch thread safety.
-rw-r--r--include/grpc/grpc.h5
1 files changed, 4 insertions, 1 deletions
diff --git a/include/grpc/grpc.h b/include/grpc/grpc.h
index 71ffaa4a01..e07376fa78 100644
--- a/include/grpc/grpc.h
+++ b/include/grpc/grpc.h
@@ -387,7 +387,10 @@ grpc_call *grpc_channel_create_registered_call(
The order of ops specified in the batch has no significance.
Only one operation of each type can be active at once in any given
batch.
- THREAD SAFETY: grpc_call_start_batch is thread-compatible */
+ THREAD SAFETY: access to grpc_call_start_batch in multi-threaded environment
+ needs to be synchronized. As an optimization, you may synchronize batches
+ containing just send operations independently from batches containing just
+ receive operations. */
grpc_call_error grpc_call_start_batch(grpc_call *call, const grpc_op *ops,
size_t nops, void *tag);