This hasn't had a response in a while so I wanted to followup again. We 
don't allow fire-and-forget or for that matter anything that would allow 
more than 1 outstanding op on the same side of a stream without an 
intervening Next (or completed AsyncNext) for two key reasons: making sure 
that we have sane concurrency guarantees and reducing the likelihood of 
OOMing because of a lack of constraints. Either of these modes of operation 
can be implemented as a layer of code on top of gRPC, so we're not 
supporting them in the C/C++ API.


On Tuesday, November 15, 2016 at 11:15:52 AM UTC-8, Nathaniel Manista wrote:
> On Wed, Nov 9, 2016 at 2:30 PM, < <javascript:>> wrote:
>> I am also interested in the fire and forget case. Is there any update on 
>> this use case?
> We talked about fire-and-forget around this time last year but didn't have 
> a compelling use case at the time. You may wish to contribute to the 
> discussion in this issue <> (don't 
> be put off that it is closed).
> -Nathaniel

You received this message because you are subscribed to the Google Groups 
"" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

Reply via email to