Re: [dev-servo] Channels and synchronous networking

2015-01-28 Thread Josh Matthews
My current line of thinking is that we send a message to the compositor that puts the pipeline in the modal state and pops up a dialog. Additionally, the message contains a Sender, with the script task waiting synchronously on the corresponding Receiver; when the alert box is closed, the compos

Re: [dev-servo] Channels and synchronous networking

2015-01-28 Thread Boris Zbarsky
On 1/28/15 7:21 AM, Josh Matthews wrote: My current line of thinking is that we send a message to the compositor that puts the pipeline in the modal state and pops up a dialog. Additionally, the message contains a Sender, with the script task waiting synchronously on the corresponding Receiver; w

Re: [dev-servo] Channels and synchronous networking

2015-01-28 Thread Josh Matthews
On 2015-01-28 3:21 PM, Boris Zbarsky wrote: On 1/28/15 7:21 AM, Josh Matthews wrote: My current line of thinking is that we send a message to the compositor that puts the pipeline in the modal state and pops up a dialog. Additionally, the message contains a Sender, with the script task waiting s

Re: [dev-servo] Channels and synchronous networking

2015-01-28 Thread Boris Zbarsky
On 1/28/15 11:49 AM, Josh Matthews wrote: Those are good points. Since those events go through the regular script event loop Should they, though? we would presumably have to process every pending script event in line before them, which could be bad? Stuff like >setTimeout(function() { windo

Re: [dev-servo] Channels and synchronous networking

2015-01-28 Thread Josh Matthews
On 2015-01-28 5:12 PM, Boris Zbarsky wrote: On 1/28/15 11:49 AM, Josh Matthews wrote: Those are good points. Since those events go through the regular script event loop Should they, though? I'm not certain what you're asking. The events come from another thread, so they need through some ki

Re: [dev-servo] Channels and synchronous networking

2015-01-28 Thread Boris Zbarsky
On 1/28/15 12:33 PM, Josh Matthews wrote: I'm not certain what you're asking. The events come from another thread, so they need through some kind of event queue. Today, that's the per-origin event loop. OK. That means, for example, that you can't navigate away from a page that's in the middle

Re: [dev-servo] Channels and synchronous networking

2015-01-28 Thread Manish Goregaokar
Perhaps if we had some sort of priority system to the queue, where high priority events (navigation, etc) override the other ones? -Manish Goregaokar On Thu, Jan 29, 2015 at 2:00 AM, Boris Zbarsky wrote: > On 1/28/15 12:33 PM, Josh Matthews wrote: > >> I'm not certain what you're asking. The ev

[dev-servo] Uniqueness and users' privacy

2015-01-28 Thread Marc Collin
I think Servo should respect users' right of privacy and make the browser get a good result at https://panopticlick.eff.org/ A good result at Panopticlick means that it shouldn't make a user too unique. Of course that can't be prevented completely, even more since it's a unique browser (at least fo

[dev-servo] .servo cache directory moved

2015-01-28 Thread Matthew Brubeck
As we discussed last month , pull request #4755 moves the ".servo" directory (where Rust/Cargo snapshots are cached) inside the source tree by default. After you pull this change and b