[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Web Workers and ArrayBuffers?
- To: Glenn Maynard <email@example.com>
- Subject: Re: [Public WebGL] Web Workers and ArrayBuffers?
- From: Kenneth Russell <firstname.lastname@example.org>
- Date: Tue, 12 Apr 2011 11:05:23 -0700
- Cc: Shy Shalom <email@example.com>, webgl public <firstname.lastname@example.org>
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1302631529; bh=pDJQ0X7nWV/590uBbnicaBrIY5g=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=VXvnrvKtRB4MAR2fbN/+r/Lxp055deEQYH/TWjKTOh7rJ6ImflP5Lnfimyoop33qK k9Ru5Hk+IN6H0wRDkPaeQ==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Scf6VUwKgsipVsPXNlE6w3ns01lGsreyf8OeUDK8+Yo=; b=mgoOoinc//I0yWZFZCEWjwUqzQo84zwkyZ/Nr3dg1kWtGZwm/GgF8rRn1gHvfirRq7 +y2twSh81tcKcPW5QM1g==
- Domainkey-signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wbOLh10JaXxcT/kb940hItEiKDJ9yhEyybVh8+LbOuGkfwQP5D6rKfa06RiLaocxnc StviqUY7z9B6VnfyVMAw==
- In-reply-to: <BANLkTikmbcdmvvDgY9zSSgdA=owORObDjA@mail.gmail.com>
- List-id: Public WebGL Mailing List <public_webgl.khronos.org>
- References: <BANLkTi=i=zvWdtRzvwf-DQiZAZX-W7+_Rw@mail.gmail.com> <BANLkTimD2T_CXT2Jr_PTFqkVHdUGSM0kCQ@mail.gmail.com> <BANLkTikmbcdmvvDgY9zSSgdA=owORObDjA@mail.gmail.com>
- Sender: email@example.com
On Tue, Apr 12, 2011 at 10:23 AM, Glenn Maynard <firstname.lastname@example.org> wrote:
> On Tue, Apr 12, 2011 at 1:07 PM, Kenneth Russell <email@example.com> wrote:
>> We are about to start revising the Typed Array specification to define
>> the behavior of passing ArrayBuffers and typed array views between the
>> main thread and worker threads. The new behavior will be zero-copy,
>> and if you ping-pong the ArrayBuffers back and forth, you'll be able
>> to implement really efficient producer-consumer queues.
> Note that there's been discussion recently on a couple mailing lists
> on the subject of zero-copy PostMessage, though it stalled out:
> "WebWorkers and images" on whatwg:
> "Using ArrayBuffer as payload for binary data to/from Web Workers" on webapps:
> I don't think this belongs in the Typed Array spec, but as part of the
> Web Messaging and Web Worker specs, to allow zero-copy messaging with
> a consistent API for any supported types. CanvasPixelArray for 2d
> canvas is another obvious candidate (though I *really* wish
> CanvasPixelArray and ArrayBuffer weren't totally separate APIs in the
> first place).
> I'm not sure how this could be done in Typed Arrays without support
> from the Web Messaging spec in the first place...
We've been hoping to keep things simple, and just specify how
ArrayBuffers and typed array views interact with the structured clone
algorithm. I think it would be appropriate to include this text in the
typed array spec, because it would keep the behavioral definition of
these types self-contained. Looking at the Web Messaging spec, I don't
think any changes would be needed in order to add this support to
You are currently subscribed to firstname.lastname@example.org.
To unsubscribe, send an email to email@example.com with
the following command in the body of your email: