Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IPC/RPC "pipe" mechanism #11

Closed
mikeptweet opened this issue Nov 1, 2018 · 2 comments
Closed

IPC/RPC "pipe" mechanism #11

mikeptweet opened this issue Nov 1, 2018 · 2 comments

Comments

@mikeptweet
Copy link

Awesome project! I noticed that this project uses the "pipe" option to launch and communicate with chrome via puppeteer. Is this mechanism documented somewhere, similar to the WebSocket debug interface?
@pavelfeldman
Copy link
Collaborator

I don't think there is any documentation.

If you launch chrome with the --remote-debugging-pipe flag, it opens stdio pipes 3 and 4 (following stdout and stderr) that allow communication over CDP with the root browser target. You can discover other targets from there. Messages are \0 separated. PipeTransport is a 70 line adapter that shows how it works.

@mikeptweet
Copy link
Author

That gives me what I need ... thanks :-)

@gregmartyn gregmartyn mentioned this issue Dec 7, 2018
Closed
@tv42 tv42 mentioned this issue Feb 15, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pavelfeldman @mikeptweet