Back to News
news

Moqintosh ships v0.14.2

Changed • Reduced Data copies on the receive hot path. • Refactored Byte​Reader to operate on slice/view-based byte access where possible. • Changed payload/bytes representation in Subgroup​Object, Object​Datagram, and…

Source: GitHubView source →

Repository Snapshot

  • Repo: t-gazzy/Moqintosh
  • Source: GitHub
  • Language: Swift
  • Last pushed: 2026-04-24
  • Milestone: Release v0.14.2
  • Published: 2026-04-17

Summary

Changed • Reduced Data copies on the receive hot path. • Refactored Byte​Reader to operate on slice/view-based byte access where possible. • Changed payload/bytes representation in Subgroup​Object, Object​Datagram, and…

Why It Matters

t-gazzy/Moqintosh is an active MOQ project, so a tagged GitHub release is a concrete milestone for implementers tracking protocol and deployment progress.

Source Excerpt

Changed • Reduced Data copies on the receive hot path. • Refactored Byte​Reader to operate on slice/view-based byte access where possible. • Changed payload/bytes representation in Subgroup​Object, Object​Datagram, and Key​Value​Pair to use Read​Only​Bytes. • Removed duplicate header reads in Stream​Receiver​Coordinator by switching header dispatch to a single-pass flow. • Updated Fetch​Object​Frame​Reader, Message​Frame​Reader, and Subgroup​Object​Frame​Reader to reduce unnecessary buffer recreation during incremental reads. • Adjusted Control​Message​Parameter, Setup​Parameter, and Authorization​Token byte handling to work with Read​Only​Bytes. Added • Added Read​Only​Bytes. • Added Stream​Receiver​Coordinator​Tests to cover header parsing and routing behavior. • Added Byte​Reader test coverage for Read​Only​Bytes view behavior. Fixed • Fixed incorrect byte-range handling when payload…

Stay ahead of MOQ

Get the latest IETF MOQ standards updates, protocol analysis, and ecosystem news delivered to your inbox.

Go deeper with MOQ Edge Pro

Weekly deep-dives, IETF standards tracking, and streaming tech trend reports — from $9/mo.

See plans →