On Wed, Jul 31, 2013 at 9:35 AM, Ehsan Akhgari <ehsan.akhgari@gmail.com>wrote: > When discussing how to fix the shared memory problem, we have either Roc's > proposal on the table which doesn't change the API surface but uses > neutering to prevent concurrent accesses to the same buffer, or Jer's > proposal which breaks the API surface and does not use neutering in order > to work around the WebKit + JSC bug. I personally think that Jer's > solution is a cleaner API, but we have decided to not fix other problems in > the API in order to maintain backwards compatibility, and I would like to > urge everybody to keep the trade-offs in mind when casting their vote. > I think once Jer clarifies the conditions under which NO_MODIFICATION_ALLOWED_ERR is fired, his proposal may have similar complexity to mine (perhaps even more complex, since he introduces the new AudioBufferChannel object and APIs to work with it). Let's wait and see. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w * *
Received on Tuesday, 30 July 2013 23:13:53 UTC