npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

cluster-proxy

v0.1.0

Published

Abstracts method calling on an object in the master process. The workers have a proxy object that abstracts all the message passing. The main limitation is that arguments and values must be JSON serializable.

Downloads

16

Readme

This module allows a clusterized node.js application to have a shared object between the master and worker processes.

Internally it uses message passing and JSON serialization of arguments and return values, so the abstraction is not perfect (objects like file references, sockets, bound functions, etc. cannot be passed around).

You can read the full generated jsdoc here: http://bazaarvoice.github.io/node-cluster-proxy/out/index.html

Example of usage

var cluster = require('cluster');
var clusterproxy = require('cluster-proxy');
if (cluster.isMaster) {
  var delegate = {
    a : 42,
    f : function(a, b) {
      return a + b;
    },
    g : function(a, cb) {
      cb(null, a*2, a*a);
    }
  };
  var master = new clusterproxy.Master({delegate: delegate});
  master.connectWorker(cluster.fork());
} else { //worker process
  var proxy = new clusterproxy.Worker();
  proxy.get('a', console.log);
  proxy.invoke('f', 1, 2, console.log);
  proxy.invokeAsync('g',//method name
                     21,//argument for the invoked method
                     function(proxyErr, delegateErr, double, square) {//callback: note that we have two error arguments, one for the cluster proxy itself (timeouts, etc.) and another for the delegate errors.
    if(!proxyErr && !delegateErr) {
      console.log('double:', double, 'square:', square);
    } else {
      console.log('error:', proxyErr || delegateErr);
    }
  });
}

Running tests

There is a monolithic test file that can be run as a normal nodejs script, or directly with npm test

TO-DO

  • Support for returned promises in delegate objects
  • Return promises in the clients