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

socketmq

v0.12.0

Published

Lightweight messaging library for node & browser.

Downloads

11

Readme

SocketMQ

Build Status Coverage Status

Lightweight messaging library for node & browser.

Messaging Types

SocketMQ supports req/rep and pub/sub messaging patterns. Messaging pattern is high level concept of how messages should be handled on sending and receiving. It's client/server & transport agnostic which means you can use all 4 types of messaging pattern no matter you are connected to a server or being connected from a client with any of the transports supported.

Request/Response

Each request will be sent to one connected client/server and wait for response (round-robin scheduler).

// example/rep.js
var socketmq = require("../");

var smq = socketmq.bind("tcp://127.0.0.1:6363");

smq.on("bind", function() {
  console.log("rep bound");
});

var event = "hello"; // or you can call it topic or channel.

smq.on("connect", function(stream) {
  console.log("new connection");
  smq.req(event, "request from server", function(msg) {
    console.log(msg);
  });
});

smq.rep(event, function(msg, reply) {
  console.log("requested msg:" + msg);
  reply("Hi " + msg + ", world!");
});
// example/req.js
var socketmq = require("socketmq");

var smq = socketmq.connect("tcp://127.0.0.1:6363");

smq.on("connect", function(stream) {
  console.log("req connected to server");
});

setInterval(function() {
  smq.req("hello", "socketmq.req", function(msg) {
    console.log("replied msg:" + msg);
  });
}, 1000);

smq.rep("hello", function(msg, reply) {
  console.log("request from server", msg);
  reply("response from client");
});

Publish/Subscribe

A pub message will be distributed to all client/server connected and no response will be sent back. It's a fire and forget messaging pattern. Pub messages could be received by subscribing to the publishing topic.

// example/pub.js
var socketmq = require("socketmq");

var smq = socketmq.connect("tcp://0.0.0.0:6363");

smq.on("connect", function() {
  console.log("pub connected");
  setInterval(function() {
    smq.pub("pub.test", "hello");
  }, 1000);
});
// example/sub.js
var socketmq = require("socketmq");

var smq = socketmq.bind("tcp://127.0.0.1:6363");

smq.on("bind", function() {
  console.log("sub bound");
});

smq.sub("pub.test", function(data) {
  console.log("got pub message: " + data);
});

Using tags

SocketMQ can tag the streams and send messages to streams with specific tags.

var socketmq = require("socketmq");

var tcpUri = "tcp://127.0.0.1:6363";
var smq = socketmq.connect(tcpUri, function(stream) {
  // Tag the stream.
  smq.tag(stream, "tcp");
});

var tlsUri = "tls://127.0.0.1:46363";
smq.connect(tlsUri, function(stream) {
  smq.tag(stream, "tls");
});

// Then send messages using `reqTag` of `pubTag`

// `req` message only to server with `tcp` tag
smq.reqTag("tcp", "hello", "message", function() {
  // ...
});

// `pub` message only to server with `tls` tag
smq.pubTag("tls", "hello", "message");