Github user masaori335 commented on the issue:
https://github.com/apache/trafficserver/pull/830
1) 256 seems crazy deep, is that a reasonable default?
SETTINGS_MAX_CONCURRENT_STREAMS is 100 at least. And "idle" streams (that
are not counted for concurrent streams) can be node of tree.
Those can be said for odd-numbered streams which is used by client and
even-numbered streams which is used by server. So I chose 256.
If we ignore server-push cases, it could be 128.
2) Do we want to make this configurable instead of static? Are there use
cases where someone want more (or less) ?
Hmm, if someone wants to increase SETTINGS_MAX_CONCURRENT_STREAMS, it looks
like this should be increased too. But this is a limit of recursion, so I don't
think this should be configurable for now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
