That makes sense, thanks for confirming. On Thursday, June 27, 2019 at 12:19:16 AM UTC+5:30, Yang Gao wrote: > > I think you can consider then read-only. The buffer is usually not changed > in-place because you do not know whether you are the only owner that holds > the ref. > > On Wednesday, June 26, 2019 at 9:22:21 AM UTC-7, Mayank Narula wrote: >> >> Hi folks >> >> I am referring to this definition - >> /// 1. static Status Serialize(const Message& msg, >> /// ByteBuffer* buffer, >> /// bool* own_buffer); >> >> Are the memory-regions referred to by slices in 'buffer' (output of >> Serialize) read-only for rest of gRPC stack? Otherwise my impl of >> Serialize() would have to copy these memory regions and then create slices >> & resulting byte-buffer. I want to avoid copy-ing these memory-regions. >> >> Thanks >> Mayank >> >
-- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/572d8ee4-e303-4d5d-bf11-04feeee7e787%40googlegroups.com.
