René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Proposal: child_process: Send socket but keep it open in parent","articleBody":"The current behavior when sending a `net.Socket` object to a child process using `child_process.ChildProcess.send()` is to close the socket in the parent. This way, only the socket receiver can read and write to it.\n\nProblem: in some use-cases, a user may want to have BOTH parent and child to write to the TCP socket. For instance, I'm developing an app where a process writes data to the socket, whereas another one writes metadata. Sharing the socket in C, not in Node.js (currently).\n\nThe enhancement I propose is to add an optional `keepOpen` parameter to specify whether the parent should keep the socket open or not (it would default to `false` to keep existing behavior).\n\n``` js\nconst child = require('child_process').fork('child.js');\nconst server = require('net').createServer();\n\nserver.listen(1234).on('connection', function (socket) {\n    child.send('socket', socket, { keepOpen: true });\n\n    // Currently this crashes with: \"Error: This socket is closed.\"\n    socket.write('-- hello from parent --');\n});\n```\n\nWhat I'm asking here is whether this is an acceptable enhancement or not. If it is, I'll start working on a clean pull request.\n","author":{"url":"https://github.com/adrienverge","@type":"Person","name":"adrienverge"},"datePublished":"2015-12-14T10:13:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/4271/node/issues/4271"}