Download JAR files tagged by bytebuffer with all dependencies

A reimplementation of java.util.BitSet, replacing the backing long[] with a java.nio.ByteBuffer

A data type similar to ByteBuffer, but can read/write bits as well as bytes to improve throughput and allow for optional compression.

A plugin to monitor usage of direct buffers created by <CODE>ByteBuffer.allocateDirect</CODE> and mapped buffers created by <CODE>FileChannel.map</CODE>. Note that the buffers monitoring requires the monitored application to run JDK 7 starting from Build 36.

Fast and memory-efficient byte buffer, an optimized version of Java's ByteBuffer class. Useful for fast low-level I/O operations like working with files or transferring data over the internet.

ArenaReturns' fork of Pbbl, a thread-safe Buffer pool that allows for the automatic reuse of Buffer objects (ByteBuffer, CharBuffer, etc.), which can be over 30x faster than allocating a new ByteBuffer when needed.

A thread-safe Buffer pool that allows for the automatic reuse of Buffer objects (ByteBuffer, CharBuffer, etc.), which can be over 30x faster than allocating a new ByteBuffer when needed.

A thread-safe Buffer pool that allows for the automatic reuse of Buffer objects (ByteBuffer, CharBuffer, etc.), which can be over 30x faster than allocating a new ByteBuffer when needed.

Fast and memory-efficient byte buffer, an optimized version of Java's ByteBuffer class. Useful for fast low-level I/O operations like working with files or transferring data over the internet.

Module that defines the HttpChannel API. HttpChannels abstract complex download and upload steps into a simple and easy to use NIO Channel. NIO Channels can be wrapped into an InputStream or OutputStream and used in any way you may find possible to. Aside from that, Channels can be used natively in most next-gen libraries, meaning that you don't even need to wrap anything, just start writing or reading data to or from the channel wth a ByteBuffer. Anyone using the library should try to rely on code from this module only and, only if necessary, on configuration classes that are implementation specific. Relying on any other resource or class is considered an error and should NOT be done. One of the most interesting usages of channels for uploads and download is that you can easily copy data straight from one channel to the other, with less than 10 lines of code! Also, channels allows the implementation of a "tee" mechanism, in which data redden from a single channel can be copied to several other channels on the fly!