[webkit-dev] GlobalScript in WebKit
dimich at chromium.org
Wed Nov 25 21:41:46 PST 2009
Thanks a lot for sharing your perspective! I really wish your reply
had, in addition to the statement of the opinion, an argument or just
more explanation of why you think so. I think we covered SharedWorkers
and inter-window communication in the previous discussions and in the
BTW, could you tell what's the 'course' that would be reverted?
On Wed, Nov 25, 2009 at 8:30 PM, Sam Weinig <sam.weinig at gmail.com> wrote:
> Hi Dmitry,
> As I have noted to others on the Chrome team, I do not think this is good
> idea and I don't think we should have it in WebKit. It adds extra
> complexity to WebKit and gives little beyond what is possible using
> inter-window communication and SharedWorkers. I think we need to give more
> time for large applications to adopt designs around workers before we
> reverse course, at which point, we should again discuss this in the
> standards community.
> On Thu, Nov 19, 2009 at 10:35 PM, Dmitry Titov <dimich at chromium.org> wrote:
>> Hi webkit!
>> I'm starting to work on actual implementation of GlobalScript experimental
>> API and started to post patches (hopefully in reviewable portions). There is
>> an uber-bug which has plan of implementation.
>> The current plan is to get it in under ENABLE_GLOBAL_SCRIPT, with both JSC
>> and v8 bindings (first with JSC because at the moment JSC bindings are
>> easier to work with and I'd wish WebKit not to have 1-engine-only features
>> I'd be glad to know if there are suggestions, ideas or concerns of any
>> kind... For example, if there is no interest in JSC bindings, it can be hard
>> to get them reviewed by someone who knows them well. It'd be better to know
>> that earlier.
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
More information about the webkit-dev