Chris Vest
14d55c3e0b
Avoid nesting composite buffers
Motivation: There is no reason that composite buffers should nest when composed. Instead, when composite buffers are used to compose or extend other composite buffers, we should unwrap them and copy the references to their constituent buffers. Modification: Composite buffers now always unwrap and flatten themselves when they participate in composition or extension of other composite buffers. Result: Composite buffers are now always guaranteed* to contain a single level of non-composed leaf buffers. *assuming no other unknown buffer-wrapping buffer type is in the mix.
Netty Incubator Buffer API
This repository is incubating a new buffer API proposed for Netty 5.
Building and Testing
Short version: just run make
.
The project currently relies on snapshot versions of the Panama Foreign fork of OpenJDK.
This allows us to test out the most recent version of the jdk.incubator.foreign
APIs, but also make building, and local development more involved.
To simplify things, we have a Docker based build, controlled via a Makefile with the following commands:
image
– build the docker image. This includes building a snapshot of OpenJDK, and download all relevant Maven dependencies.test
– run all tests in a docker container. This impliesimage
. The container is automatically deleted afterwards.dbg
– drop into a shell in the build container, without running the build itself. The debugging container is not deleted afterwards.clean
– remove the leftover containers created bydbg
,test
, andbuild
.build
– build binaries and run all tests in a container, and copy thetarget
directory out of the container afterwards. This is the default build target.
Description
Languages
Java
99.6%
Dockerfile
0.2%
Makefile
0.2%