-
Notifications
You must be signed in to change notification settings - Fork 124
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.
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
Mark WebTransport streams keep alive #1389
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comments on the issue.
7b6b9b1
to
355fdde
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think you have the right places for these calls.
You need one for the server and one for the client.
I think that the client one goes in webtransport_create_session and the server one goes in webtransport_accept_session.
The points you have identified are about streams created within the session, not the session stream.
Finally, I would like to see test cases for this, showing that keep-alives (PING) are sent if the connection is left to go idle for too long, with only a webtransport session active. There are test cases for keep-alive that you can base this on.
@MayyaSunil are you still intending to land this change? |
@larseggert, thanks for checking. |
@MayyaSunil any update on when you might get to this? |
I will resume this early next week and hope to complete by the end of the week |
OK. Making this a draft PR until it's ready for review, please change it back then. |
355fdde
to
09d431e
Compare
Benchmark resultsPerformance differences relative to 2463618.
Client/server transfer resultsTransfer of 134217728 bytes over loopback.
|
@MayyaSunil is this good to go functionality-wise? Does it still need a test? |
@larseggert Its not okay functionality wise and needs a test |
CC @jesup |
Failed Interop TestsQUIC Interop Runner, client vs. server, differences relative to 9143d73. neqo-latest as client
neqo-latest as server
All resultsSucceeded Interop TestsQUIC Interop Runner, client vs. server neqo-latest as client
neqo-latest as server
Unsupported Interop TestsQUIC Interop Runner, client vs. server neqo-latest as client
neqo-latest as server
|
Webtransport newbie here. Trying to help wrap this up.
The call to
I've made that addition, and added a test. WDYT? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1389 +/- ##
=======================================
Coverage 95.39% 95.39%
=======================================
Files 113 113
Lines 36683 36682 -1
=======================================
Hits 34993 34993
+ Misses 1690 1689 -1 ☔ View full report in Codecov by Sentry. |
This PR is intended to resolve #1369