[webkit-dev] GlobalScript in WebKit
dimich at chromium.org
Thu Nov 26 09:44:20 PST 2009
What I meant was it would be nice, for the sake of discussion, to share the
experience of real life applications that used SharedWorkers or inter-window
communications for sharing of significant portions of code and data. Google
apps may be a partial example but it is a real life example of concrete
issues with proposed solution that sounds pretty generic and useful for
other web apps. It is only prudent to take their feedback rather then
replace it with our own theories about future of the web. No doubt this is a
new mechanism and it's good to question it, since it has costs even as
experimental API. Gut feelings vary, some app devs say they need it to solve
real issues, we dont hear from other app devs who were facing similar issues
and solved it differently. Seems there is no strong argument to kill it nor
bless it. Why don't make it experimental and see? If it was possible to
implement it in extension or plugin, we would run it as another Gears-like
experiment, but it can not be done in a plugin... I believe there could be
good arguments that simply didn't surface yet, and hope to hear them.
On Wed, Nov 25, 2009 at 10:16 PM, Peter Kasting <pkasting at google.com> wrote:
> On Wed, Nov 25, 2009 at 9:41 PM, Dmitry Titov <dimich at chromium.org> wrote:
>> BTW, could you tell what's the 'course' that would be reverted?
> Meaning, "before we decide that SharedWorkers and inter-window
> communication are insufficient, and a further proposal should be entertained
> by the standards community".
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev