[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] using the same context with multiple canvases
I don't know the details of Ian's proposal, but it sounds like the 'proxy' would formalize the transfer of the context.
In the case of Firefox' HW accelerated canvas, Mozilla could wrap their DirectX object so it can be passed to a different thread where it would then be unrolled.
On Fri, Nov 9, 2012 at 9:33 PM, Gregg Tavares (社用) <firstname.lastname@example.org>
What does the proxy object add?
One idea webgl has discussed is that you could transfer a context and it would get transfered by ownership, same as ArrayBuffer does now. The old context object in the passer would enter the "contextlost" state. This would let you just transfer the context directly. Mozilla has pointed out that 2D canvas now also needs contextlost support because of GPU acceleration so adding that to canvas 2D would let it use the same solution. No need for a proxy