53d2e4b955
Motivation: Buffers should always behave the same, regardless of their underlying implementation and how they are allocated. Modification: The SizeClassedMemoryPool did not properly reset the internal buffer state prior to reusing them. The offsets, byte order, and contents are now cleared before a buffer is reused. Result: There is no way to observe externally whether a buffer was reused or not.
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 must 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– remote the debugging container created bydbg.build– build binaries and run all tests in a container, and copy thetargetdirectory out of the container afterwards. This is the default build target.