W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2013

Re: [whatwg] Canvas in workers

From: David Bruant <bruant.d@gmail.com>
Date: Sun, 13 Oct 2013 18:22:16 +0200
Message-ID: <525AC8B8.20806@gmail.com>
To: Glenn Maynard <glenn@zewt.org>, Kyle Huey <me@kylehuey.com>
Cc: whatwg <whatwg@whatwg.org>, Robert O'Callahan <robert@ocallahan.org>
Le 13/10/2013 18:12, Glenn Maynard a écrit :
> On Sun, Oct 13, 2013 at 11:01 AM, David Bruant <bruant.d@gmail.com> 
> wrote:
>>     bool commit();
>>> Boolean as return value for success? :-s
>> A promise instead maybe? throw instead of false at least?
>> In any case, it looks like commit could be a long operation (tell me if
>> I'm wrong here. Do you have numbers on how long it takes/would take?),
>> having it async sounds reasonable.
>
> This should be synchronous and never block.
I might have misused the word "async" again, sorry about that. I think 
we agree.

> Even if the Canvas is in a
> different process, it should be possible to do this with IPC without
> waiting for the other side to process the change.
How does a worker know when the changes on the screen happened? I 
imagine a worker would want to know that before performing other changes 
to the canvas.

David
Received on Sunday, 13 October 2013 16:22:43 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:11 UTC