W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: [webcomponents]: Moving custom element callbacks to prototype/instance

From: Hajime Morrita <morrita@google.com>
Date: Thu, 7 Mar 2013 09:30:08 +0900
Message-ID: <CALzNm5qh31Y3OjrrrWoQwUyLdSzXGmGMeDYiSLHmkJH994yoWw@mail.gmail.com>
To: Erik Arvidsson <arv@chromium.org>
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>
On Thu, Mar 7, 2013 at 9:13 AM, Erik Arvidsson <arv@chromium.org> wrote:

> 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.
>

Right. We can just Get() can Call() it. Possible saving by caching these
functions in C++ side is the Get() call then.


>
> --
> erik
>
>
>


-- 
morrita
Received on Thursday, 7 March 2013 00:30:36 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT