)]}'
{
  "commit": "9e75db181609abbe2120ff918ca8b5611c757efe",
  "tree": "c6e529db5862ed93f337c2a84bc58ff010db0380",
  "parents": [
    "f41bf64c347693484d5ffeab03fd85674bb0f2a7"
  ],
  "author": {
    "name": "QUICHE team",
    "email": "quiche-dev@google.com",
    "time": "Tue Apr 02 17:21:31 2019 -0400"
  },
  "committer": {
    "name": "Victor Vasiliev",
    "email": "vasilvv@google.com",
    "time": "Wed Apr 03 00:09:25 2019 +0000"
  },
  "message": "Set QUIC\u0027s max packet size to whatever Quartc configures.\n\nCurrently, Quartc only configures the max packet size on the packet writer.\nHowever, the QuicConnection keeps its own, separate max packet size.  This is\nset from a constant in quic_constants.h (kDefaultMaxPacketSize \u003d 1350 for\nclients or kDefaultServerMaxPacketSize \u003d 1000 for servers).\n\nCalling QuicConnection::SetMaxPacketLength() updates the connection\u0027s value to\nmatch the packet writer\u0027s value.\n\nThe effect can be confirmed by running Quartc tests.  Before this change, we saw\n1000 bytes as the max packet size on the server:\nPacket size stats\u003d[mean \u003d 349, stddev \u003d 394, min \u003d 19, max \u003d 1000, 25% \u003d 36, 50% \u003d 130, 75% \u003d 787, 90% \u003d 1000]\n\nAfter this change, we observe 1200 bytes as the max packet size in both\ndirections:\nPacket size stats\u003d[mean \u003d 262, stddev \u003d 432, min \u003d 19, max \u003d 1200, 25% \u003d 29, 50% \u003d 35, 75% \u003d 141, 90% \u003d 1200]\n\ngfe-relnote: n/a (Quartc only)\nPiperOrigin-RevId: 241603141\nChange-Id: I9da1c0dcfa37af22c2f0decdf27f9081eec22444\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9517e0b6259793d004d02108c47e896764eb8aaa",
      "old_mode": 33188,
      "old_path": "quic/quartc/quartc_factory.cc",
      "new_id": "436212fd7a1bc3cbfeb13f5a9b12cf1fde150154",
      "new_mode": 33188,
      "new_path": "quic/quartc/quartc_factory.cc"
    }
  ]
}