Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

stashback

Package Overview
Dependencies
Maintainers
4
Versions
11
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

stashback

Stashes callbacks for later execution

  • 1.1.3
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
13K
increased by5.37%
Maintainers
4
Weekly downloads
 
Created
Source

Stashback

NPM version NPM downloads Build Status Code Climate Test Coverage Code Style Dependency Status devDependencies Status

Stashback is a library for stashing and retrieving callbacks in a decoupled request/response workflow. Its primary use case is to enable code within an http request/response sequence to publish a message to an ESB, e.g. RabbitMQ and wait for a reply.

Installation

npm install stashback

Example Usage (Express)

var rabbitmq = require('./my-rabbitmq-client')
var express = require('express')
var format = require('util').format
var uuid = require('node-uuid').v4
var stashback = require('stashback')({ timeout: 5000 })

var app = express()

app.get('/greet/:id', function(req, res, next) {

    // Generate a unique id for the callback
    var callbackId = uuid()

    // Define the callback
    var callback = function(err, user) {
        if (err) return next(err)
        res.send(format('Hello %s', user.name))
    }

    // Stash the callback for later execution
    stashback.stash(callbackId, callback, function(err) {

        // An error will occur if you've used a duplicate callbackId.
        if (err) return next(err)

        // Publish the message to the ESB, requesting user for the specified id. Using rabbitmq as an example.
        rabbitmq.publish({ callbackId: callbackId, userId: req.params.id })
    })
})

app.listen(3000)


function onMessage(message) {

    // When we receive the user response unstash the callback using the callbackId specified in the message
    stashback.unstash(message.callbackId, function(err, callback) {

        // Execute the callback passing it the user object (the callback will be a no-op if something went wrong)
        callback(err, message.user)
    })
}

Callback Expiry

In order to prevent a slow memory leak and to abort slow running requests it's a good idea to configure stashback with a timeout. This can be done globally and for each 'stash' operation. See the api for more details.

Duplicates

Attempting to 'stash' multiple callbacks with the same id results in an error. Attempting to 'unstash' a callback twice (or after it has expired) results in both an error and a no-op callback being returned. i.e.

stashback.unstash('never-stashed-or-expired', function(err, callback) {
    assert.equal(err.message, 'Unknown key: never-stashed-or-expired')
    assert.equal(typeof callback, 'function')
})

Further Customisation

You can further customise stashback's behaviour by providing your own onDuplicateKey, onUnknownKey and onExpiry handlers. See the api for more details.

Keywords

FAQs

Package last updated on 05 Jul 2020

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc