8941fab5fa
Motivation: Different protocols will prefer to use different default byte order, so it makes sense if our buffers support a configurable byte order as well. Modification: Break all accessor methods into 3 variants; one that uses default (configured) byte order, and two others that use big- and little-endian, respectively. Result: Buffers can be allocated with any byte order desired, and this byte order can even be changed later in rare cases where that's useful. The Buf API also has accessors that explicitly uses BE or LE byte order, for when you don't want to rely on the configured default.
Netty Incubator Buffer API
This repository is incubating a new buffer API proposed for Netty 5.