New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Evaluate ConnectionTracingKey as connection tracking #19

Open

everesio opened this issue Jun 7, 2024 · 0 comments

Assignees

Labels

Contributor

everesio commented Jun 7, 2024

quic-go/quic-go in the v0.45.0 provides a breaking change regarding ConnectionTracingKey. Evaluate it as a possibility for connection tracking.

Breaking Changes

Connection.NextConnection now takes a context and correctly handles handshake failures (#4551)
qlog: DefaultTracer was renamed to DefaultConnectionTracer (#4556)
The ConnectionTracingKey is now deprecated. Use Transport.ConnContext to set your own tracing key (#4532)

everesio added the enhancement label

everesio self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment