[Public WebGL] WebGL2 and no mapBuffer/mapBufferRange

Zhenyao Mo [email protected]
Wed Mar 4 10:15:02 PST 2015

On Wed, Mar 4, 2015 at 10:10 AM, Florian Bösch <pya[email protected]> wrote:
> On Wed, Mar 4, 2015 at 7:07 PM, Zhenyao Mo <[email protected]> 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 [email protected]
To unsubscribe, send an email to [email protected] with
the following command in the body of your email:
unsubscribe public_webgl

More information about the public_webgl mailing list