FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

doc: describe process API for IPC by sam-github · Pull Request #1978 · nodejs/node · GitHub

/ node Public

doc: describe process API for IPC - #1978

Merged
sam-github merged 1 commit into
nodejs:masterfrom
sam-github:doc-process-ipc
Sep 9, 2015
Merged

doc: describe process API for IPC#1978
sam-github merged 1 commit into
nodejs:masterfrom
sam-github:doc-process-ipc

Conversation

Copy link
Copy Markdown
Contributor

mscdex added doc Issues and PRs related to the documentations. process Issues and PRs related to the process subsystem. labels Jun 15, 2015
Comment thread doc/api/process.markdown Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Backticks

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

nit: They will be received as messages rather than They will be received as a message

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

@thefourtheye backticks aren't supported there, the markdown syntax I used is consistent with other places in docs where events are linked to.

@Trott thanks for all the comments, I will incorporate

Copy link
Copy Markdown
Contributor

@sam-github Did you get a chance to address the review comments?

Copy link
Copy Markdown
Contributor Author

comments addressed, @thefourtheye @Trott

Copy link
Copy Markdown
Contributor Author

@nodejs/collaborators ping, docs for otherwise undocumented node APIs, can I get a thumbs up?

Comment thread doc/api/process.markdown Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Documentation references should be in this format I think [text][] and then at the bottom of the page, [text]: relative url. PTAL at #2142 for reference.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Why? There are over a hundred examples in the API docs of the markup above, including one to this specific event.

Separating out to a ref at the bottom is useful when there are multiple uses made of that ref, otherwise I don't see the point.

If there is a stylistic or technical reason to change all markdown refs to the format you used in #2142, writing a tool to convert them all would be a good way, but that is out of scope here.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Oh okay. Actually I received a comment in that PR, so I thought that that is the standard which we follow.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

@thefourtheye the comment on #2142 was from me. It wasn't about having the link at the bottom of the page, just that the URL needed to be relative (without the https://iojs.org/api/ part). It is fine to have it inline.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

@targos Ah, I see it now. Thanks for clarifying man :-) @sam-github Sorry about that comment, please ignore it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

No problem, thanks for your attention.

Copy link
Copy Markdown
Contributor

Maybe a small italized disclaimer like *{Method,Event} applies to child processes only.* would be appropriate after the description of each?

Copy link
Copy Markdown
Contributor Author

@silverwind There is a disclaimer:

If io.js was not spawned with an IPC channel, process.{send, disconnect}() will be undefined.

How would you suggest this be enhanced? Italics around it the entire sentence? "spawned" changed to "spawned as a child process"? You can't get spawned as anything but a child process, so that seems oddly worded to me, but YMMV.

I'm happy to patch in any specific wording or markup to get this wrapped up.

Copy link
Copy Markdown
Contributor Author

@nodejs/collaborators this is stalled, can I get a review?

Comment thread doc/api/process.markdown Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

ChildProcess should probably be in backticks.

cjihrig commented Aug 6, 2015

Copy link
Copy Markdown
Contributor

LGTM minus my comments.

Copy link
Copy Markdown
Contributor

ping @sam-github

Copy link
Copy Markdown
Contributor Author

I'll have time to try the new merge job this weekend, not enough network ATM.

Copy link
Copy Markdown
Contributor

@sam-github We've suspended using that for now. It wasn't working out to well at the current time.

Comment thread doc/api/process.markdown Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

as of 607aa3a this should be process.send(message[, sendHandle][, callback]) I believe

Comment thread doc/api/child_process.markdown Outdated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Suggestion: write as net.Socket and net.Server and make them links to the appropriate sections in net.markdown. Ditto in process.markdown.

Copy link
Copy Markdown
Member

LGTM with suggestions.

sam-github force-pushed the doc-process-ipc branch 2 times, most recently from 204d0b5 to 92e55ff Compare September 9, 2015 16:42

Copy link
Copy Markdown
Contributor Author

@bnoordhuis OK, I also found that when you added the callback it invalidated some refs to child.send() because the anchor link changed. @cjihrig you were working on a link checker, weren't you, how's that going?

Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: nodejs#1978
sam-github merged commit f442904 into nodejs:master Sep 9, 2015
sam-github deleted the doc-process-ipc branch September 9, 2015 16:49

cjihrig commented Sep 9, 2015

Copy link
Copy Markdown
Contributor

@cjihrig you were working on a link checker, weren't you, how's that going?

That wasn't me. Maybe @chrisdickinson? A lot of people seem to confuse us.

Copy link
Copy Markdown
Member

dgram.Socket (from dgram.createServer()) is also supported.

Copy link
Copy Markdown
Contributor

\o/

sam-github added a commit that referenced this pull request Sep 11, 2015
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
PR-URL: #1978
rvagg mentioned this pull request Sep 12, 2015
Fishrock123 mentioned this pull request Sep 13, 2015
7 tasks

Copy link
Copy Markdown
Contributor

Should references to "io.js" be replaced with "node.js"? I found 2 in a quick scan of these changes.

cjihrig commented Sep 13, 2015

Copy link
Copy Markdown
Contributor

Yes. Would you care to make a PR @tflanagan

Copy link
Copy Markdown
Contributor

#2846

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to the documentations. process Issues and PRs related to the process subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.


Back | FazBrowse Home | New Git URL