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

node-traffic

v1.2.1

Published

A nodejs semaphore implementation.

Downloads

2

Readme

Traffic

A node.js semaphore implementation.

Single node semaphore

Usage

var traffic = require('node-traffic');

traffic.enter(function criticalZone () {
// ...
traffic.leave();  
});

Example with web servers

app.post('/resource', function (req, res) {
  traffic.enter(function () {
    // DB stuff...
    traffic.leave();
    res.respond();
  });
});

Namespaced semaphores

traffic.enter('changeResource', function criticalZone () {
  // ...
  traffic.leave('changeResource');
});

Example for web servers

app.post('/resource/:id', function (req, res) {
  traffic.enter('changeResource-' + req.params.id, function () {
    // DB stuff...
    traffic.leave('changeResource-' + req.params.id);
    res.respond();
  });
});

Distributed semaphore

Traffic allows to have a distributed semaphore across multiples nodes using Zookeeper.

Configure

var config = {
  zkHost: 'localhost:2181', // host:port
  zkRoot: '/', // znode path
  zkTimeout: 4000 // 4 seconds
};
var traffic = require('node-traffic').distributed(config);
traffic.on('connectionTimeout', function (err) {
  // handle Zookeeper connection timeout
});

zkRoot will be created if it doesn't exists.

Usage

traffic.enter(function criticalZone () {
  // ...
  traffic.leave();
});

// Namespaced
traffic.enter('myNamespace', function () {
  // ...
  traffic.leave('myNamespace');
});

Note: Using namespaces creates znodes under config.zkRoot.

Don't forget to close the Zookeeper connection...

process.on('exit',function(){
  traffic.close();
});

Common patterns

If traffic fails to connect to Zookeeper you can fallback into normal semaphores.

traffic.on('connectionTimeout', function (err) {
  traffic = require('node-traffic');
});

Run tests

Install jasmine

npm install -g jasmine

Run specs

npm test
jasmine spec/semaphore_spec.js
jasmine spec/distributed_semaphore_spec.js