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

consensus-manager

v1.0.0

Published

consensus manager for a distributed topology

Downloads

3

Readme

###consensus-manager

####consensus wrapper for a distributed topology

The consensus manager listens and stores responses from remote peers until the consensus is reached. The consensus is reached depending on the strategy implemented.

The consensus manager controls:

  • time it takes to reach consensus
  • accepts and stores responses from peers
  • notices upper layer when consensus is reached and its output (if any)

The strategy defines:

  • when consensus is reached

####installation

sudo npm install consensus-manager

####example


Strategy         = require('..')
ConsensusManager  = require('ConsensusManager') 

var strategy = new Startegy(strategy_opts)  
var consensus = new ConsensusManager(strategy)  


consensus.on('listening', function(){
  //event fired when consensus manager is initialized
})

consensus.on('consensus', function(result, time_diff){
  //event fired when consensus is reached
})

consensus.on('noListening', function(){
  //event fired when a peer's response arrives but consensus has been reached
})



//init consensus manager
consensus.init// ... stuff happen, user sent a response

//...
 
//peer answers. consensus manager processes its response
consensus.process(response)