Thanks to visit codestin.com
Credit goes to github.com

Skip to content

rexfordkelly-on-nodejs/IPCEE

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

31 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

IPC EE Build Status

IPC combined with EventEmitter2

What for?

First, RTFM child.send(message[, sendHandle]).

The sendHandle option to child.send() is for sending a TCP server or socket object to another process. The child will receive the object as its second argument to the message event.

This means that you won't be able to do things like:

child.send('message', {some: 'data'}, [data])

List of accepted instances. If you look a but further in the code, internal messages are sent with the first argument. As stated in the docs:

There is a special case when sending a {cmd: 'NODE_foo'} message.

Then, I thought it could be nice to do:

Child

ipc.send('started')

Master

var child = fork('child')
child.once('started', dosomething)

Internally I just had to combine EventEmitter and use the first argument to pass an array of arguments.

Usage

Child

  var ipc = IPCEE(process)

  ipc.send('started')

  ipc.on('ping', function() {
    ipc.send('pong') 
  })

Master

  var server = fork('some/node/app.js')
  var client = IPCEE(server)

  client.once('started', function() {
    client.send('ping')
  })

  client.once('*.pong', function() {
    console.log('\o/')
  })

Or with namespaces:

Child

  var ipc = IPCEE(process, {wildcard: true})

  ipc.send('started')

  ipc.on('ping:me', function() {
    ipc.send('me:pong')
  })

Master

  var server = fork('some/node/app.js')
  var client = IPCEE(server, {wildcard: true})

  client.once('started', function() {
    client.send('ping.*')
  })

  client.once('*.pong', function() {
    console.log('\o/') 
  })

Caveat

Using the first argument of child_process.send(), Nodejs IPC will transport strings. Javascript objects are encoded with json internally. That said, You won't be able to pass instances.

Example:

process.on('uncaughtException', function(err) {
  ipc.send('error', err.toString(), err.stack)

  process.nextTick(function() {
    process.exit(1) 
  })
})

Here, Temptation would be to send the full Error object but JSON.stringify(new Error('test')) will return '{}'.

Native IPC features

IPCEE does not override any of the internals methods. This means that you'll still be able to get messages from the standard way:

process.on('message', function(m, handle) {
  if(m === 'server') {
    //do something with handle 
  }
})

But it will handle accepted instances in an easy way too. For example, sending a Socket:

//server.js
ipc.send('socket', sock)
//child.js
ipc.on('socket', function(sock) {
  assert(sock instanceof Socket)
})

Licence

The MIT License (MIT)

Copyright (c) 2015 Antoine Bluchet

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

About

IPC combined with EventEmitter

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 100.0%