Re: [webcomponents]: Moving custom element callbacks to prototype/instance from Erik Arvidsson on 2013-03-07 (public-webapps@w3.org from January to March 2013)

From: Erik Arvidsson <arv@chromium.org>
Date: Wed, 6 Mar 2013 19:13:50 -0500
To: Hajime Morrita <morrita@google.com>
Cc: Dimitri Glazkov <dglazkov@google.com>, Scott Miles <sjmiles@google.com>, public-webapps <public-webapps@w3.org>, Elliott Sprehn <esprehn@google.com>, Steve Orvell <sorvell@google.com>, Daniel Buchner <daniel@mozilla.com>, Adam Klein <adamk@google.com>, Blake Kaplan <mrbkap@mozilla.com>, William Chen <wchen@mozilla.com>
Message-ID: <CAJ8+GoijRMqO=6z+3zKd65ttvcxv3u+-NPObD=A4bSOXwoo8dA@mail.gmail.com>

Inline

On Wed, Mar 6, 2013 at 7:03 PM, Hajime Morrita <morrita@google.com> wrote:

> One consequence is that it will become harder to cache (including negative
> cache) these values. We need to traverse the prototype chain in C++, which
> is typically slower than doing it in JS, on every lifecycle event. Or we
> need to invent something cool to make it fast.
>

There is no reason to walk the prototype chain from C++ (speaking from
WebCore+V8/JS experience). You can invoke the method using the V8/JSC APIs.

-- 
erik

Received on Thursday, 7 March 2013 00:14:38 UTC