On 1/15/13 2:48 AM, Brendan Eich wrote:
I don't buy it. Processes are heavy enough, especially on mobile
devices, that Chrome pragmatically limits the number in the pool and
shares non-HTTPS (last I heard, someone correct me if this has changed
materially).
My point was that if they're doing process per origin, effectively, then
we can put different origins in different DOM Rust tasks. We don't have
to use separate processes for them (though we should perhaps design with
the option of doing so) but we _can_ run them in parallel, kill them
independently of each other, and so forth. I'm slightly more interested
in that than in the crash-proofing aspects, though obviously I like
those too.
Or put another way, you'll be able to nuke all those ad iframes without
affecting the site that embeds them.
Process per iframe? How about per img?
Just because we have the option of using a process doesn't mean we have to.
Note that the linked-to document has some discussion about how this
should interact with the renderer process limit in Chrome.
Good point about expanded principals. I'm not sure of the b2g details
(will ask around and report back) but I've proposed that cross-site
scripts (script src="http://ads-r-us.com/...") should be given a
distinct trust label that's subordinate in the lattice to the including
page's origin-label.
I think the point is that if we ever want WebKit to actually implement
our b2g stuff, we should ensure that any non-same-origin communication
is async in our designs.
-Boris
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo