We need to decide whether TBuffer should be used as object for serialized bytes.
Pros: reuse of existing code, backward compatibility, easy interfacing with TStreamerInfo
Cons: splitting TBuffer from libCling is non-trivial (but likely possible, including changing the inheritance / injecting a new inheritance level that does not need TObject), byte swap, memory management (e.g. versus mmap / handling of padding bytes).
Open questions: performance, cost of splitting libCling out, what's really left if we only use TBuffer without steamer info? So first answer "do we want to use TStreamerInfo?"