Skip to content
This repository has been archived by the owner on Aug 11, 2020. It is now read-only.

TODO: Implement special handling for out of packet numbers error #58

Closed
jasnell opened this issue Aug 21, 2019 · 0 comments
Closed

TODO: Implement special handling for out of packet numbers error #58

jasnell opened this issue Aug 21, 2019 · 0 comments

Comments

@jasnell
Copy link
Member

jasnell commented Aug 21, 2019

A QuicSession is limited to a fixed maximum number of packets that may be sent. Once this number is exhausted, the connection must be torn down. We should likely handle this case in a special way that lets the user attempt to recover by quickly opening a new session if they want.

Also need to figure out how to test this.
jasnell added a commit to jasnell/quic that referenced this issue Dec 3, 2019
@jasnell
quic: record pkt_num_exhausted error
ed629f0 
Fixes: nodejs#58
jasnell added a commit to jasnell/quic that referenced this issue Dec 4, 2019
@jasnell
quic: record pkt_num_exhausted error
9d72cad 
Fixes: nodejs#58
@jasnell jasnell closed this as completed in ac49529 Dec 4, 2019
addaleax pushed a commit that referenced this issue Dec 11, 2019
@jasnell @addaleax
quic: record pkt_num_exhausted error
c7a10c9 
Fixes: #58
PR-URL: #207
Reviewed-By: #207
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jasnell