Skip to content

SwiftQUIC: Expose remote datagram frame size through connection metadata#46

Merged
agnosticdev merged 2 commits into
mainfrom
agnosticdev/UsableDatagramFrameSize
Jul 10, 2026
Merged

SwiftQUIC: Expose remote datagram frame size through connection metadata#46
agnosticdev merged 2 commits into
mainfrom
agnosticdev/UsableDatagramFrameSize

Conversation

@agnosticdev

Copy link
Copy Markdown
Collaborator

Expose remote datagram frame size through connection metadata for API consumption.

}
}

public func getRemoteDatagramFrameSize() -> UInt16 {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The value for this transport parameter can't change so I wonder if it's better/simpler to model on activeConnectionIDLimit, and just set it once — no locks, no callbacks, etc

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is value in this approach too, but this starts to fragment the current pattern we have today.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in 72a6981

@agnosticdev agnosticdev merged commit 76d7587 into main Jul 10, 2026
23 checks passed
@agnosticdev agnosticdev deleted the agnosticdev/UsableDatagramFrameSize branch July 10, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants