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

pooling

v0.4.6

Published

General purpose resource pool API

Downloads

1,459

Readme

Overview

pooling is a small general purpose resource pooling library. It is heavily inspired from James Cooper's excellent generic-pool library. This library was written after using that library for some time and desiring extra functionality (namely watching events and health checking).

Usage

var EventEmitter = require('events').EventEmitter;
var pooling = require('pooling');

var pool = pooling.createPool({
        checkInterval: 30000, // 30s (default is 30s)
        max: 10,              // Default is 1
        maxIdleTime: 120000,  // 2m (default is 1 hour)
        name: 'my pool',

        // Health check. Call the callback with an Error if you want
        // to indicate this client should die. destroy will still be
        // called (i.e., don't "double free").
        //
        // This function is called when an object is unused for
        // >= maxIdleTime.  If you don't provide a check function,
        // the default behavior is to mark the client for death.
        check: function check(client, callback) {
                if ((client.id % 2) !== 0)
                            return callback(new Error());

                return callback(null);
        },

        // callback is of the form function (err, client).
        create: function create(callback) {
                var client = new EventEmitter();
                client.id = Math.floor(Math.random() * 1000);
                return callback(null, client);
        },

        // destroy is for you to do cleanup with; the pool will have already
        // discarded the object (hence no callback)
        destroy: function destroy(client) {
                client.was = client.id;
                client.id = -1;
        }
    });

    pool.on('create', function (client) {
            console.log('client %d created', client.id);
    });

    pool.on('death', function (client) {
            console.log('client %d was killed', client.was);
    });

    pool.on('drain', function () {
            console.log('pool has no backlog or outstanding clients');
    });

    pool.acquire(function (err, client) {
            if (err) {
                    console.error('Unable to acquire: %s', err.stack);
                    process.exit(1);
            }

            pool.release(client);
            client.emit('error', new Error('die now'));
    });

    // Gracefully block future acquire calls and wait for clients to be
    // released
    pool.shutdown(function () {
            console.log('done');
            process.exit(0);
    });

By default the pool will remove clients on close, end, error and timeout events. You can override this by passing in an events array at pool creation time. You can also pass in a Bunyan Logger - pooling logs everything at the trace level.

Install

    npm install pooling

Development

To run unit tests and lint/style checks, just run:

    make prepush

You can generate coverage data by running:

    make cover

And opening ./cover_data/index.html.

License

The MIT License (MIT) Copyright (c) 2012 Mark Cavage

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.