I started prototyping the async networking redesign. To make the
up-front work easier, I've added a layer of abstraction so consumers can
opt-in to receiving async replies so I don't need to rewrite everything
all at once. This has led me to a discovery - our current implementation
of sync XHR
On Tue, Jan 27, 2015 at 10:10 PM, Josh Matthews
wrote:
> I started prototyping the async networking redesign. To make the up-front
> work easier, I've added a layer of abstraction so consumers can opt-in to
> receiving async replies so I don't need to rewrite everything all at once.
> This has le
We don't have the notion of a global event loop or anything. We
effectively have an event loop per script task (ie. event loop per TLD),
but no ability to spin it arbitrarily at the moment. The benefit of
using channels for some forms of communication is that they side-step
the event loop and c
Tree is open. Review/rebase all the things; there's some backlog in the
PR queue.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Caspy7 in #servo pointed me towards an explanation of new vsync
integration in Gecko:
http://www.masonchang.com/blog/2015/1/22/project-silk . How's Servo
stack up against the state of the art here?
___
dev-servo mailing list
dev-servo@lists.mozilla.or
On 1/27/15 5:46 PM, Josh Matthews wrote:
We don't have the notion of a global event loop or anything. We
effectively have an event loop per script task (ie. event loop per TLD),
but no ability to spin it arbitrarily at the moment.
How do you plan to implement alert()? Do you plan to allow an a
6 matches
Mail list logo
