)]}'
{
  "commit": "21f546d0d6b2938d6a8305079ed26c8e49d4f5e2",
  "tree": "378da824a66d4b780c1211827d709a1214169609",
  "parents": [
    "ff8c2aedfee6514ba50391dcf5fef5bd02016684"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Sun Feb 05 16:12:55 2012 +0000"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Sun Feb 05 16:12:55 2012 +0000"
  },
  "message": "Merge of r4384, r4385:\n\nFixes for limit_rate:\n\n*) Fixed throughput problems with large limit_rate.\n\n   Previous attempt to fix this was in r1658 (0.6.18), though that one\n   wasn\u0027t enough (it was a noop).\n\n*) Fixed interaction of limit_rate and sendfile_max_chunk.\n\n   It\u0027s possible that configured limit_rate will permit more bytes per\n   single operation than sendfile_max_chunk.  To protect disk from\n   takeover by a single client it is necessary to apply sendfile_max_chunk\n   as a limit regardless of configured limit_rate.\n\n   See here for report (in Russian):\n   http://mailman.nginx.org/pipermail/nginx-ru/2010-March/032806.html\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "46351349cf5c6a527165b3bd01c87b30c7a5ce40",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_write_filter_module.c",
      "new_id": "a9660ee1fd2bea54e555bfa3caf551ad7f036a9f",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_write_filter_module.c"
    }
  ]
}