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

redis-ipc-qs

v1.0.6

Published

Redis-ipc request-response model.

Downloads

6

Readme

============ redis-ipc-qs

Intro


Simple nodejs library to communicate over redis-ipc. qs in title stands for reQuest/reSponse.

Example server usage:

.. code-block:: javascript

const Server = require('redis-ipc-qs').Server;
let myServer = Server((req, res) => {
  console.log('got request', req);

  // Here we handle request
  res.method = req.method;
  res.payload = req.payload;
  res.send();
});


myServer.on('error', console.log);

myServer.listen('0000');

Example client usage:

.. code-block:: javascript

const Client = require('redis-ipc-qs').Client;

let myClient = Client({timeout: 1000});

myClient
  .listen('0001')
  .then(_ => {
      console.log('making  request');
      myClient
        .request('0000', {method: 'hello', payload: 42})
        .then(res => {
          console.log(`Server responded with ${JSON.stringify(res)}`);
        })
        .catch(e => console.log(`Error occured: ${e.message}`));
  })
  .catch(e => console.log(`aaaarg ${e.message}`));
  

There are not more than five musical notes, yet the combinations of these five give rise to more melodies than can ever be heard. There are not more than five primary colors (blue, yellow, red, white, and black), yet in combination they produce more hues than can ever been seen. There are not more than five cardinal tastes (sour, acrid, salt, sweet, bitter), yet combinations of them yield more flavors than can ever be tasted. In battle, there are not more than two methods of attack - the direct and the indirect; yet these two in combination give rise to an endless series of maneuvers. The direct and the indirect lead on to each other in turn. It is like moving in a circle - you never come to an end. Who can exhaust the possibilities of their combination?

Requests and responses are restricted only by two fields: "method" and "payload". The rest depends on you.

Usage


.. code-block:: javascript

let myServer = Server((req, res) => {// handler});

// with params
let myServer = Server((req, res) => {// handler}, {
  debug: true,
  path: '/var/run/redis/redis.sock'
});


let myClient = Client();
// with params
let myClient = Client({
  debug: true,
  path : '/tmp/redis.sock'
  timeout: 5000
});

By default path parameter is "/var/run/redis/redis.sock". You may also try to set path to redis url: "redis://user:password@host:port". Client request timeout default value is 5000ms.