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

pmongo-lock

v0.1.2

Published

Simple locking mechanism for promised-mongo

Downloads

7

Readme

Simple locking mechanism for promised-mongo

example

var pmongo = require("promised-mongo");
var db = pmongo("test");
var pmongolock = require("pmongo-lock");
var Lock = pmongoLock(db);
var lock = new Lock("test");
lock.lock().then(function() {
    //...
    return lock.unlock();
});

How does this locking module work?

First we create a class (Lock) with the promised-mongo MongoDB database instance being bound to it.

Then we create a new lock object with some key (for example, if we lock a file, the key may be the name of that file).

After that we call the .lock() method of the lock object which returns a promise resolving when the lock is acquired.

When we finish our work, we call the .unlock method of the lock object which also returns a promise resolving when unlocking is done.

When a lock is acquired by a lock object, other locks with the same key will wait until the first object releases the lock.

Pending locks are added to the queue (UUIDs are used to identify the objects). Read/write locks has higher priority than readonly ones.

There are two locking modes: readonly and read/write. A lock may be acquired by one or more readonly lockers or by a single read/write locker at the same time, exclusively.

Use Lock.ReadOnly or Lock.ReadWrite to specify locking mode. If not specified, locking mode defaults to read/write.

Let's review Configuration

Currently there is only one configuration option:

options.retryDelay = 10;

options.retryDelay

retryDelay is the number of milliseconds to wait before retrying to acquire the lock.