parsefrom(Bytebuf) is unsafe

[cbornet]

Very nice initiative ! I'll have a look at how to integrate into gRPC and use it in Pulsar-gRPC

Since parseFrom does zero-copy, I understand that the Bytebuf passed as argument must not be released as long as the deserialized object may be used. So the name of the operation should probably reflect that? For instance, the classic protobuf lib uses the name unsafeWrap (in UnsafeByteOperations). WDYT ?

[aahmed-se]

We may to wrap the buffers with agrona

https://dzone.com/articles/agronas-threadsafe-offheap