Skip to content

Releases: SlickQuant/slick-stream-buffer

Release v1.0.3

12 Jun 02:56

Choose a tag to compare

Changes

  • slick/dynamic_stream_buffer.h is now installed only when Boost is found at
    configure time, and the header emits a clear #error when included without
    Boost.Asio on the include path. The core slick/stream_buffer.h remains
    Boost-free.

Release v1.0.2

11 Jun 19:50

Choose a tag to compare

Changes

  • Added SlickStreamBuffer::discard() to drop committed-but-unconsumed bytes (and any
    prepared region) without publishing them — for invalidating a partial message after a
    connection drops mid-read. Older published records remain subject to the existing
    lossy overwrite semantics.
  • Added dynamic_stream_buffer::clear() (matching beast::flat_buffer::clear()), which
    forwards to discard().
  • Update slick-shm fetching version to 0.1.4
  • Auto fetch slick-shm if not found in config cmake

Release v1.0.1

11 Jun 01:20

Choose a tag to compare

Changes

  • Fixed SlickStreamBuffer::prepare(0) so it no longer discards an outstanding
    prepared region before commit().
  • Fixed dynamic_stream_buffer::data() so its returned buffer size respects the
    adapter max_size() cap and stays consistent with size().
  • Reduced producer-side atomic load traffic by keeping local committed/consumed
    cursor shadows for the single-producer hot path.
  • Added regression tests for zero-length prepare handling and DynamicBuffer
    data()/size() consistency.

Release v1.0.0

11 Jun 01:05

Choose a tag to compare

Changes

Initial release.

  • slick::SlickStreamBuffer — lock-free single-producer multi-consumer byte stream
    buffer with local memory and shared memory support (slick-shm), monotonic message
    records, independent consumer cursors, lossy overwrite semantics with loss
    detection, and contiguous readable region with wrap relocation.
  • slick::dynamic_stream_buffer — Boost.Asio DynamicBuffer_v1 adapter, drop-in
    replacement for boost::beast::flat_buffer; consume(n) publishes the consumed
    bytes to consumers as one message record (zero-copy fan-out).
  • GoogleTest suites for local memory, shared memory, and the asio adapter
    (including a real TCP loopback test); CI for Windows/Linux/macOS.