W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

Re: [Web MIDI API] Examples and a serializer

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Mon, 17 Dec 2012 17:33:10 +0000
To: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>
Message-ID: <F4847EB5FE0F45C8A0E5404A89953A34@gmail.com>


On Monday, December 17, 2012 at 5:28 PM, Jussi Kalliokoski wrote:

> On Mon, Dec 17, 2012 at 7:01 PM, Marcos Caceres <marcosscaceres@gmail.com (mailto:marcosscaceres@gmail.com)> wrote:
> > Our Input (MIDIPort) is a host object, so it can be treated as a structured clone. So I think we are sweet there. However, we need to look at how to specify that properly.
> > 
> > Need to find some examples of things that can be passed around safely to worker contexts (I've little experience with workers, but happy to help do the research if you point me in the right direction).
> 
> Ok, great news! I've added a bug for this: https://www.w3.org/Bugs/Public/show_bug.cgi?id=20415
Excellent.  
> Transferables are defined here: http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#transferable-objects and AFAIK currently only implemented for ArrayBuffers, but also in the proposal Hixie made for Canvas in Web Workers, canvas contexts would be transferable. I don't know of any precedents for copyable host objects. :/ But that would be preferable in our case, since ports with read access have only read access and ports with write access have only write access, so I can't think of possible race conditions.
> 

Thanks for the pointer. I'll have a read. 

-- 
Marcos Caceres
Received on Monday, 17 December 2012 17:33:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:04 UTC