On Tue, Jul 16, 2013 at 11:37 AM, Patrick Walton wrote:
> Right, that's been on our mind as well. We try to use channels and ports
> wherever we can. In general channels and ports are better than IDs in every
> way: they cannot be forged and have better memory management properties (as
> integer I
On 7/15/13 4:32 PM, Robert O'Callahan wrote:
A minor random thought related to that design:
Using integer IDs, as Gecko does, raises the possibility of a bug,
possibly even a security bug, where a rogue IFRAME is able to render
itself at the wrong place in the tree. In Gecko, preventing a
compro
A minor random thought related to that design:
Using integer IDs, as Gecko does, raises the possibility of a bug, possibly
even a security bug, where a rogue IFRAME is able to render itself at the
wrong place in the tree. In Gecko, preventing a compromised process from
doing an attack like that re
Robert O'Callahan wrote:
"people like roc say we must be at least as fast as Gecko for everything"
To be clear: I think Servo's architecture must not prevent Servo from being
as fast as Gecko for everything. I push for microbenchmarks targeting the
risky parts of Servo's architecture because we
On 7/15/13 3:58 PM, Robert O'Callahan wrote:
For compositing with IFRAMEs, you might want to consider what we do for
multi-process compositing in Gecko. It's somewhat obvious but it seems like
it works well. Each process publishes a layer tree to the compositor. A
layer tree can contain RefLayers
For compositing with IFRAMEs, you might want to consider what we do for
multi-process compositing in Gecko. It's somewhat obvious but it seems like
it works well. Each process publishes a layer tree to the compositor. A
layer tree can contain RefLayers, each with a unique ID. A layer tree root
can
"people like roc say we must be at least as fast as Gecko for everything"
To be clear: I think Servo's architecture must not prevent Servo from being
as fast as Gecko for everything. I push for microbenchmarks targeting the
risky parts of Servo's architecture because we must avoid discovering much
On Jul 15, 2013, at 1:11 PM, Boris Zbarsky wrote:
> On 7/15/13 3:05 PM, Josh Matthews wrote:
>> https://github.com/mozilla/servo/wiki/Meeting-2013-07-15
>
> Some comments on the discussion (sorry I couldn't make the meeting, and thank
> you for the notes!):
>
> 1) Mutable prototypes will be su
On 7/15/13 3:05 PM, Josh Matthews wrote:
https://github.com/mozilla/servo/wiki/Meeting-2013-07-15
Some comments on the discussion (sorry I couldn't make the meeting, and
thank you for the notes!):
1) Mutable prototypes will be supported in SpiderMonkey (and indeed
are), but they will likely
https://github.com/mozilla/servo/wiki/Meeting-2013-07-15
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
10 matches
Mail list logo
