[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] WebGL2 and no mapBuffer/mapBufferRange

On Wed, Mar 4, 2015 at 10:10 AM, Florian Bösch <pyalot@gmail.com> wrote:
> On Wed, Mar 4, 2015 at 7:07 PM, Zhenyao Mo <zmo@chromium.org> wrote:
>> Basically we can't just return the pointer from glMapBufferRange to
>> the javascript in read-only or write-only modes, because there is no
>> mechanism to enforce read-only or write-only.
> So what you're saying is there isn't a ReadOnlyArrayBuffer and
> WriteOnlyArrayBuffer correct? If I'm not mistaken, returning ArrayBuffer
> conformant objects, which impose additional restrictions shouldn't be
> terribly hard.

You also need to consider some browsers (for example, Chrome) runs GPU
in a separate process.  Copying data out and copying data back is the
only way to implement this.

You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl