On Thu, Apr 30, 2009 at 11:40 AM, Darin Fisher da...@chromium.org wrote:
On Tue, Apr 28, 2009 at 6:22 PM, Aaron Boodman a...@chromium.org wrote:
On Tue, Apr 28, 2009 at 6:18 PM, Michael Nordman micha...@chromium.org
wrote:
+ chromium-dev
Can you please explain what you think has
The story is even simpler for localStorage. Everything is fairly self
contained and the only way it cares about the main thread is in asserts to
verify SQLite is not used on the main thread.
My guess is that the story for what's considered the main thread will change
for each API much like the
On Wed, Apr 29, 2009 at 7:02 AM, Peter Kasting pkast...@chromium.orgwrote:
On Tue, Apr 28, 2009 at 6:38 PM, Jeremy Orlow jor...@chromium.org wrote:
Darin was there on that lunch and was actually the one who first suggested
running parts of WebCore in the browser to me during a 1:1. :-)
On Wed, Apr 29, 2009 at 7:43 AM, David Levin le...@google.com wrote:
On Wed, Apr 29, 2009 at 7:02 AM, Peter Kasting pkast...@chromium.orgwrote:
On Tue, Apr 28, 2009 at 6:38 PM, Jeremy Orlow jor...@chromium.orgwrote:
Darin was there on that lunch and was actually the one who first
I think it's a great idea and the only drawback I can see is the WTF
dependency and the security implications, which shouldn't be anything
we couldn't overcome.
The biggest challenges IMHO would be:
1) clearly identifying what backend and frontend mean and where the
separation occurs. I worry
Yup, I'm looking to work thru things in a similar fashion with anders
(original appcache author).
On Wed, Apr 29, 2009 at 11:53 AM, David Levin le...@google.com wrote:
I think how to split/refactor depends on the feature, understanding the
current code, and working with the appropriate webkit
On Tue, Apr 28, 2009 at 5:27 PM, Michael Nordman micha...@google.comwrote:
In some sense we do have separate process in which to run sandboxed
'backend' code relevant to multiple renders if the need arises... the
worker process.
The way you stated this is a bit odd, but on the surface I
I have always felt like running the WebCore backend in the browser
process with an IPC channel between it and the frontend was a really
elegant design for this problem. And I never really understood why we
weren't allowed to depend on WebCore (even indirectly) in the browser
process. Is the idea
Well, the question comes down to this: Can we trust running small amounts of
WebCore in the browser process.
Historically, the answer to running WebCore in the browser has been a
resounding no. Can you please explain what you think has changed since such
decisions were made (or why it's time to
+ chromium-dev
Can you please explain what you think has changed since such decisions were
made (or why it's time to revisit such decisions)?
I don't think there was code in webcore suitable for this purpose
before... html parsing, javascript,sql interpretting... all dangerous
from a
On Tue, Apr 28, 2009 at 6:26 PM, Evan Martin e...@chromium.org wrote:
On Tue, Apr 28, 2009 at 5:59 PM, Aaron Boodman a...@chromium.org wrote:
Is the idea that someday the browser and renderer processes
might be separate binaries?
Though this shouldn't drive your decision, about 50% of our
11 matches
Mail list logo
