diff options
| author | enal@chromium.org <enal@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-01 18:49:00 +0000 |
|---|---|---|
| committer | enal@chromium.org <enal@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-01 18:49:00 +0000 |
| commit | bba8669ac315e0710b9b544c93d3e4ab6734911b (patch) | |
| tree | da768293faed8e59d7efb7ca00d631cb491f8ff5 /third_party | |
| parent | d1a149dab6387603f81a60760214ed7dd2ebcd6e (diff) | |
| download | chromium_src-bba8669ac315e0710b9b544c93d3e4ab6734911b.zip chromium_src-bba8669ac315e0710b9b544c93d3e4ab6734911b.tar.gz chromium_src-bba8669ac315e0710b9b544c93d3e4ab6734911b.tar.bz2 | |
Prepare ppapi for chrome audio changes. Now chrome writes length of audio data
to buffers, thus allowing to correctly handle short audio streams (e.g. sound
effects in games).
Those changes allows ppapi to handle both "old" and "new" audio streams, you
can find out if stream is "old" or "new" by amount of data you get when
receiving request from the socket. After chrome changes would be checked in
"old" code path can be safely removed.
Corresponding chrome change is http://codereview.chromium.org/7328030/.
BUG=http://code.google.com/p/chromium/issues/detail?id=78992.
PS. After several comments I changed chrome code to make it much harder for
code to get buffer overrun. I was pointed that native client can write bogus
size of data into buffer, so function in chrome that reads size of data now
has extra argument -- max size of buffer, and returns min(max size of buffer,
size of data reported by client). This way min() is always called.
Review URL: http://codereview.chromium.org/7523008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@94947 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party')
0 files changed, 0 insertions, 0 deletions