Experimental API that separates out the concern of memory allocation.
◆ ConstMultiBuf
MultiBuf interface with read-only data and the option of adding layered data views.
◆ MultiBuf
MultiBuf interface with mutable data and the option of adding layered data views.
◆ TrackedConstMultiBuf
Basic MultiBuf interface with read-only data that notifies its observer, if set, on change. It has the option of adding layered data views.
◆ TrackedFlatConstMultiBuf
Basic MultiBuf interface with read-only data that notifies its observer, if set, on change.
◆ TrackedFlatMultiBuf
Basic MultiBuf interface with mutable data that notifies its observer, if set, on change.
◆ TrackedMultiBuf
Basic MultiBuf interface with mutable data that notifies its observer, if set, on change. It has the option of adding layered data views.
◆ MultiBufProperty
Basic properties of a MultiBuf.
Enumerator |
---|
kConst | Indicates the data contained within the MultiBuf is read-only. Note the difference from the MultiBuf itself being const , which restricts changes to its structure, e.g. adding or removing layers.
|
kLayerable | Allows adding or removing layers to create different views of the underlying data. This is useful with a "bottoms-up" approach to building a high-level application view out of a series of low-level protocol packets.
|
kObservable | Allows setting an Observer that is notified when bytes or layers are added or removed. One possible usage is as part of a flow control scheme, to update the flow control whenever a certain number of bytes are processed.
|