GitShow/facebook/mvfst
facebook

mvfst

An implementation of the QUIC transport protocol.

by facebook
Star on GitHubFork

C++

1.7k stars291 forks464 contributorsActive · 4h agoSince 2018MIT

Meet the team

See all 464 on GitHub →
mjoras
mjoras486 contributions
jbeshay
jbeshay449 contributions
kvtsoy
kvtsoy279 contributions
hanidamlaj
hanidamlaj184 contributions
ahornby
ahornby130 contributions
lnicco
lnicco115 contributions
wez
wez113 contributions
r-barnes
r-barnes89 contributions

Languages

View on GitHub →
C++89.5%
Python5.2%
CMake2.7%
Starlark2.2%
Shell0.2%
C0.1%
Other0.1%

Commit activity

Last 12 weeks · 250 commits

Full graph →

Community health

4 of 6 standards met

Community profile →
75
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Active · Last activity 4h ago
See all on GitHub →
kcelestinomaria
docs: align contributor license wording with project licenseOpenPR

Summary Correct the contributor license wording from BSD to MIT. Motivation The repository's file identifies mvfst as MIT licensed, while incorrectly described contributions as being licensed under BSD. This change aligns the contributor guidance with the project's actual license. This is a documentation-only correction with no runtime or API impact. Validation Confirmed the first line of is . Confirmed the stale BSD wording is absent from . Ran .

kcelestinomaria · 1mo ago

Recent fixes

View closed PRs →
afrind
Fix gcc build of DatagramFlowManager nested queue typesMergedPR

gcc fails to compile this header because the F14FastMap member instantiates traits over QueuedDatagram and DatagramFlowQueue while their default member initializers are still being parsed, so the implicitly defaulted constructors are not usable yet. Give both structs a user-provided default constructor instead of , which delays the constructor definition until the enclosing class is complete. Construction behavior is unchanged: the member initializers still supply the same defaults.

afrind · 5d ago
zzz6519003
this repo is 25MB, is it too big for an implementation of the QUIC transport protocol?ClosedIssue
zzz6519003 · 1w ago
davide03-bit
Out of order packets in ACK_RECEIVE_TIMESTAMPS FrameClosedIssue

Hi, I am studying the QUIC extension for ACK_RECEIVE_TIMESTAMPS frame. In the draft they say that timestamps are not allowed for packets received out of order. Is that true in mvfst implementation, or there is a way to handle this?

davide03-bit · 2w ago
Structured data for AI agents

Repository: facebook/mvfst. Description: An implementation of the QUIC transport protocol. Stars: 1657, Forks: 291. Primary language: C++. Languages: C++ (89.5%), Python (5.2%), CMake (2.7%), Starlark (2.2%), Shell (0.2%). License: MIT. Open PRs: 11, open issues: 25. Last activity: 4h ago. Community health: 75%. Top contributors: mjoras, jbeshay, kvtsoy, hanidamlaj, ahornby, lnicco, wez, r-barnes, afrind, deadalnix and others.

·@ofershap

Replace github.com with gitshow.dev