Skip to content

Conversation

@eugeneo
Copy link

@eugeneo eugeneo commented May 18, 2016

Interrupt V8 to process frontend connection

@pavelfeldman - please take a look

pavelfeldman and others added 3 commits May 16, 2016 10:54
This change introduces experimental v8-inspector support. This brings
the DevTools debug protocol allowing Node.js to be debugged with
Chrome DevTools native, or through other debuggers supporting that
protocol.

Partial WebSocket support, to the extent required by DevTools, is
included. This is derived from the implementation in Blink.

This code is currently behind a --with-inspector configure flag.
Pick up v8 inspector from [1]. This is the standalone version of the
devtools debug protocol.

[1] https://github.com/repenaxa/v8_inspector/commit/6dd87365

void Run() override {
agent_->SetConnected(connected_);
int pending = agent_->SafeSetAndGetField(agent_->pending_connected_,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is right. The only way to implement it correctly is to serialize connect/disconnect messages with the actual commands, i.e. to reuse the message queue for connect/disconnect. That way input such as ", message 1, message 2, message 3, , , message 10, message 11, message 12, " would be processed in order.

@ofrobots ofrobots force-pushed the v8-inspector branch 6 times, most recently from 73b9c32 to 0af8865 Compare May 25, 2016 21:52
@ofrobots ofrobots force-pushed the v8-inspector branch 6 times, most recently from 09efcf8 to 10c9ffe Compare May 29, 2016 23:48
@eugeneo eugeneo closed this Jun 8, 2016
@eugeneo eugeneo deleted the interrupt_on_connect branch June 8, 2016 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants