41b3c02812
Motivation: Thread-confinement ends up being too confusing to code for, and also prevents some legitimate use cases. Additionally, thread-confinement exposed implementation specific behavioural differences of buffers, where we would ideally like all buffers to always behave the same, regardless of implementation. Modification: All MemorySegment based buffers now always use shared segments. For heap-based segments, we avoid the overhead associated with the closing of shared segments, by just not closing them, and instead just leave the whole thing for the GC to deal with. Result: Buffers can now always be accessed from multiple different threads at the same time.
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.