Currently, RSocket follows Netty style of managing refCnt which is somewhat challenging (and not necessarily needed to be like in pure Netty).

Therefore, I would like to propose redesign that and follow Reactor-Netty way to manage refCnt, so we will be responsible for releasing a Payload and a user will be in charge of retaining content when it moves to a different thread.

Such a way of managing refCnt will simplify future adoption of Aeron (Aeron Buffers are releasing right after the execution, so if one need to move it to a different thread, the Buffer should be copied)