I am currently writing a prototype of a debugger server for Servo that
works with the Chrome Debugging Protocol:
https://github.com/ejpbruel/servo/tree/acceptor
The Chrome Debugging Protocol works by first sending a HTTP request to
http://localhost:/json (where is the remote debugging
port). This
As I mentioned in my previous post, I am trying to use the rust-websocket
library to implement a prototype debugger server for Servo.
The main server thread needs to wait for one of the following events:
1. An incoming WebSocket connection.
2. A message from the browser
Unfortunately, the former
On Mon, Sep 12, 2016 at 1:14 PM, Eddy Bruel wrote:
> The way I see it, we have two options. Personally, I'm leaning towards
> option two, but I wanted to get your opinion:
>
> 1. Ignore the problem for now. Most debugger clients for the Chrome
> Debugging Protocol can attach to a WebSocket URL dir
On Mon, Sep 12, 2016 at 1:45 PM, Eddy Bruel wrote:
> 3. I found another websocket library for Rust, called "ws". Unlike
> rust-websocket, ws seems to have a proper shutdown story (one can call a
> shutdown() method on a Sender, which can be cloned between threads). It
> also seems to be a bit more
> In addition to feeling less novel, QuickChecking JS
> APIs doesn't feel quite as useful for Servo testing (based on the
> assumption that Servo will be re-using *Monkey).
Most of the JS APIs are part of the DOM and not the built in objects.
These are implemented in the browser itself, not in Spi
We are delighted to announce that Josh Matthews is joining the Servo
core team (https://github.com/servo/servo/wiki/Governance).
Josh (jdm on IRC and GitHub) has driven planning for the DOM for
several years, coordinates most of our community programs, and is
already a contributor to other major d
It's weird to say welcome, because it's jdm who introduced me to my first
few servo bugs. But welcome anyway!!
Shing
2016年9月12日 18:09，"Lars Bergstrom" 寫道：
> We are delighted to announce that Josh Matthews is joining the Servo
> core team (https://github.com/servo/servo/wiki/Governance).
>
> Josh
>
> This may be a silly question, but why doesn't hyper come with
> WebSockets support out of the box? It seems like "part of" HTTP to
> some extent.
>
Sorry this is offtopic from the subject, but just wanted to address the
question:
You won't find websockets in hyper for the same reason you won'
You could always have some random-generated-at-startup "shutdown token"
that you send through the WebSocket server itself, triggering it to break
out of the loop.
On Mon, Sep 12, 2016 at 10:33 AM Sean McArthur
wrote:
> >
> > This may be a silly question, but why doesn't hyper come with
> > WebSo
9 matches
Mail list logo
