gr1ffon/quic-go
1
0
Fork 0
forked from quic-go/quic-go
Code Pull Requests Activity

don't apply a limit to the number of outgoing streams

Browse Source
This commit is contained in:
Marten Seemann
2017-10-15 14:56:03 +07:00
parent 480db80da1
commit 925a52f032
3 changed files with 3 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
internal/protocol/server_parameters.go
View File

@@ -56,9 +56,6 @@ const DefaultMaxReceiveConnectionFlowControlWindowClient = 15 * (1 << 20) // 15
// This is the value that Chromium is using
const ConnectionFlowControlMultiplier = 1.5
// MaxOutgoingStreams is the maximum number of streams that we will open to a peer
const MaxOutgoingStreams = 100
// MaxIncomingStreams is the maximum number of streams that a peer may open
const MaxIncomingStreams = 100
@@ -70,7 +67,7 @@ const MaxStreamsMinimumIncrement = 10
// MaxNewStreamIDDelta is the maximum difference between and a newly opened Stream and the highest StreamID that a client has ever opened
// note that the number of streams is half this value, since the client can only open streams with open StreamID
const MaxNewStreamIDDelta = 4 * MaxOutgoingStreams
const MaxNewStreamIDDelta = 4 * MaxIncomingStreams
// MaxSessionUnprocessedPackets is the max number of packets stored in each session that are not yet processed.
const MaxSessionUnprocessedPackets = DefaultMaxCongestionWindow