Excellent question! From a C++ API perspective, we only guarantee that any part of the Write (including serialization) is done when the tag is posted, so the only safe option is to keep the data valid until the tag is posted. This may become an issue, for example, for serialization alternatives or optimizations.
Regards, Vijay On Thursday, December 29, 2016 at 8:30:05 AM UTC-8, Christian Rivasseau wrote: > > Hi, > > in ClientAsyncReaderWriter::Write(const T& msg, tag), > is it OK do delete 'msg' after Write() returns, or should it be > kept alive until 'tag' was notified? > > Thanks a lot, > > > -- > Christian Rivasseau > Co-founder and CTO @ Lefty <http://www.lefty.io> > +33 6 67 35 26 74 > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/e46bcf4d-b91e-471a-ab10-697df04e7194%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
