microsoft/msquic

QUIC_STREAM_EVENT_SEND_COMPLETE should include the number of buffers sent

Open

#5,290 opened on Jul 28, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)C (671 forks)github user discovery
Area: CoreTriagedexternalfeature requesthelp wanted

Repository metrics

Stars
 (4,712 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the feature you'd like supported

It would be nice if the event data of QUIC_STREAM_EVENT_SEND_COMPLETE contained the number of buffers (count) that were initially passed into StreamSend.

Proposed solution

This would make it easier to build zero-copy implementations when send buffering is disabled so that data can be freed easily after sending has completed.

Additional context

No response

Contributor guide

Research direction
Examine the definition of QUIC STREAM EVENT SEND COMPLETE in the header files and trace how StreamSend interacts with the event completion. Identify where the buffer count is available and how to add it to the event data structure.
Tech stack
c
Domain
networking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CQUIC protocol basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60