)]}'
{
  "commit": "f8bed21638790b6d748cd04178fea36ccce79ec2",
  "tree": "5fff00e285340d9e4ff6ee8ad29f03dd12d69268",
  "parents": [
    "ad29c8ab022f0f2c6a18c8279b1db2230acfa59b"
  ],
  "author": {
    "name": "Steven Hartland",
    "email": "steven.hartland@multiplay.co.uk",
    "time": "Thu Jun 04 09:58:11 2020 +0000"
  },
  "committer": {
    "name": "Ian Lance Taylor",
    "email": "iant@golang.org",
    "time": "Tue Sep 07 21:54:12 2021 +0000"
  },
  "message": "http2: limit client initial MAX_CONCURRENT_STREAMS\n\nPrevent the client trying to establish more streams than the server is willing to accept during the initial life time of a connection by limiting `maxConcurrentStreams` to `100`, the http2 specifications\nrecommended minimum, until we\u0027ve received the initial `SETTINGS` frame from the server.\n\nAfter a `SETTINGS` frame has been received use the servers `MAX_CONCURRENT_STREAMS`, if present, otherwise use `1000` as a reasonable value.\n\nFor normal consumers this will have very little impact, allowing a decent level of concurrency from the start, and for highly concurrent consumers or large bursts it will prevent significant number of rejected streams being attempted hence actually increasing performance.\n\nFixes golang/go#39389\n\nChange-Id: I35fecd501ca39cd059c7afd1d44090b023f16e1e\nGitHub-Last-Rev: 0d1114d3a558cefed17008aba3e4a4d7b2ad3866\nGitHub-Pull-Request: golang/net#73\nReviewed-on: https://go-review.googlesource.com/c/net/+/236497\nReviewed-by: Brad Fitzpatrick \u003cbradfitz@golang.org\u003e\nTrust: Brad Fitzpatrick \u003cbradfitz@golang.org\u003e\nTrust: Joe Tsai \u003cjoetsai@digital-static.net\u003e\nRun-TryBot: Brad Fitzpatrick \u003cbradfitz@golang.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dc31cfd752d69c6da31e97a9473cd358eae9aacf",
      "old_mode": 33188,
      "old_path": "http2/transport.go",
      "new_id": "7d5c876ad400daad1e412d5d1fd514f9dc97374a",
      "new_mode": 33188,
      "new_path": "http2/transport.go"
    }
  ]
}