[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Shared resources between contexts
- To: Mark Callow <firstname.lastname@example.org>
- Subject: Re: [Public WebGL] Shared resources between contexts
- From: Kenneth Russell <email@example.com>
- Date: Thu, 5 Jan 2012 11:15:02 -0800
- Cc: Florian Bösch <firstname.lastname@example.org>, Patrick Cozzi <email@example.com>, firstname.lastname@example.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:x-system-of-record:content-type:content-transfer-encoding; bh=vpW5NSszScqxhIx0vjREErNVGhZYUIgisPLu0RLmwyk=; b=PykapZCtgKfkF/EUEBFySG2PPRZ6yaBAlbS/wSLTgxbX3J6lJhHdrnXa11hEbtmNIU YmCeetgUBTi6/0PfpUwupMQYXpBiypARJfTqjnx+m3zTYBx4ulR5ztXuoKLBEKaWJKXz mAkldTJJ17t60il1SGDuqngpE4A5i+GHt0i18=
- In-reply-to: <4F054224.email@example.com>
- List-id: Public WebGL Mailing List <public_webgl.khronos.org>
- References: <CAMDuWHecmJhxUsTddom3UFhrHw6CVNX9-5Np7+u7nsdPCZfrfirstname.lastname@example.org> <CADWO2T86uVPd=M9VXMihqR+C23EYJs3O3c30iSyGNafie63yemail@example.com> <CAMDuWHfHWjgZuuyFU43Hx+pzYeLQ42idMy0+Asy_xOuTTwAxwA@mail.gmail.com> <CABirCh-YP=zPUaMbmUz4AYojGrWztinu6EOd5Wr7SLWs5B4SFQ@mail.gmail.com> <CAP2c7GHpAmRPP6UY=rxSz6biHi+hnPTCCLq-kP4zbam41p_u4A@mail.gmail.com> <CAOK8ODivNcUF8N7Be+xEh7_SV1J4z_9AX+CYeVVbE_yRL_OMEA@mail.gmail.com> <4F054224.firstname.lastname@example.org>
- Sender: email@example.com
On Wed, Jan 4, 2012 at 10:24 PM, Mark Callow <firstname.lastname@example.org> wrote:
> #3 is not already possible. The HTML5 canvas spec. says
> "If the getContext() method has already been invoked on this element for the
> same contextId, return the same object as was returned that time"
> and if the WebGL spec. says anything to contradict that, I could not find
> it. Mind you Section 2 could use some work. It says
> "the author must obtain a [context] for a given [canvas] as described below"
> but fails to say what the author actually has to do. It only says what the
> user agent has to do. The requirement to return the same object is cleverly
> hidden by the words "when ... a new" in the introduction to the user agent's
The canvas spec defines the requirement to return the same object from
different calls to getContext() with the same context ID:
(Mark, you're correct; it is not possible to create multiple WebGL
contexts against the same canvas. Having two references to the same
context object is not the same as having two distinct contexts, each
of which can render to the canvas.)
Figuring out how to define resource sharing between WebGL contexts is
the next important step forward. Florian, as you point out, drawing
the same content to multiple canvases can be implemented by the
application if resource sharing is supported, so I don't think this
should be explicitly added to the Canvas or WebGL APIs.
> On 29/12/2011 23:16, Florian Bösch wrote:
> There seem to be 3 basic concepts of interaction far as I could see:
> #1 Sharing of resources between different contexts (buffers, textures)
> #2 Sharing one context between different canvas instances and selection of
> frontbuffer to target a particular canvas. This seems to be a special case
> of #1 and can be fully satisfied with resource sharing (also please don't
> use the term "multiple render targets" for this. That term is reserved for a
> different feature).
> #3 Using multiple contexts for one canvas (kind of context linking). This is
> already possible with getting the context of an existing canvas.
You are currently subscribed to email@example.com.
To unsubscribe, send an email to firstname.lastname@example.org with
the following command in the body of your email: