)]}'
{
  "commit": "8dfd5f96515ca20c4eb109cb0ee28e2bb32fc505",
  "tree": "efe8a11fd65642f3a7c3c22ad53609827eb797f8",
  "parents": [
    "fb74e5903914b9ec8c80b6f7a35da000f9f92ae7"
  ],
  "author": {
    "name": "Daniel P. Berrange",
    "email": "berrange@redhat.com",
    "time": "Mon Oct 09 16:54:07 2017 +0100"
  },
  "committer": {
    "name": "Daniel P. Berrange",
    "email": "berrange@redhat.com",
    "time": "Mon Oct 16 16:57:08 2017 +0100"
  },
  "message": "io: get rid of bounce buffering in websock write path\n\nCurrently most outbound I/O on the websock channel gets copied into the\nrawoutput buffer, and then immediately copied again into the encoutput\nbuffer, with a header prepended. Now that qio_channel_websock_encode\naccepts a struct iovec, we can trivially remove this bounce buffering\nand write directly to encoutput.\n\nIn doing so, we also now correctly validate the encoutput size against\nthe QIO_CHANNEL_WEBSOCK_MAX_BUFFER limit.\n\nReviewed-by: Eric Blake \u003ceblake@redhat.com\u003e\nSigned-off-by: Daniel P. Berrange \u003cberrange@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3762707b9ce0c8a5824dcc2b55ceaa50806df392",
      "old_mode": 33188,
      "old_path": "include/io/channel-websock.h",
      "new_id": "a7e5e92e61ee9cf0e1608eb3af7290909b13640d",
      "new_mode": 33188,
      "new_path": "include/io/channel-websock.h"
    },
    {
      "type": "modify",
      "old_id": "93c06f5b94cf3cac7a274a0defd85897bd82c049",
      "old_mode": 33188,
      "old_path": "io/channel-websock.c",
      "new_id": "e82b1beab306582772b919804236f46200c82bcd",
      "new_mode": 33188,
      "new_path": "io/channel-websock.c"
    }
  ]
}
