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

wsmsgbroker

v1.7.2

Published

WebSocket message broker using native WebSocket implementation and a lightweight full-JSON encoded protocol scheme

Downloads

13

Readme

WSMsgBroker

WebSocket message broker using native WebSocket implementation and a lightweight full-JSON encoded protocol scheme

Client API

var WSMsgBroker = require('wsmsgbroker');

// assuming you have a WSMsgBroker.Server running at ws://localhost:9042/foo
var client0 = new WSMsgBroker('client0', 'localhost', 9042, 'foo');
var client1 = new WSMsgBroker('client1', 'localhost', 9042, 'foo');

client1.on('registered', function () {
  client1.on('message', function (msg, response) {
    console.log('client1 received > '+msg);
    response.send('Hi to you too, sir.');
  });

  client0.send('Hi there', 'client1', function (from, answer) {
    console.log('client0 received an answer from '+from+' > '+answer);

    // but you can also send messages without callback
    // resulting in "response" to be null for the receiver :)
    client0.send({complex: 'thing'}, 'client1');
  });
});

Client.send(msg, dest, callback)

msg: {Mixed} The thing you want to send (/!\ it HAS TO be serializable by JSON.stringify(...))
dest: {String|Array} Your message receiver(s) (determined by the id used at the creation of the client)
callback: [optional] {Function} if set, it will allow a receiver to answer (fastest wins)

Protocol

clients -> server
Clients can initiate 4 actions with the servers:

  • register
  • unregister
  • send
  • answer

server -> clients
Servers can answer with 4 actions to the clients:

  • answer
  • message
  • registered
  • unregistered

WSMsgBroker expects JSON-encoded strings to be send accross the network
Below is the list of JSON-encoded clients -> server actions

register - register a client on the server

  • "id" a unique ID that identifies this client on the server
{
    "action": "register",
    "id": <AN_ID>
}

unregister - unregister a client from a server

{
    "action": "unregister"
}

send - send a message to one (or more clients)

  • "dest" must be a string or an array of strings
{
    "action": "send",
    "dest": [ <AN_ID>, <ANOTHER_ID> ],
    "message": <A_MSG>
}

answer - send an answer to a received message

{
    "action": "answer",
    "message": <A_MSG>
}

Below is the list of JSON-encoded server -> clients actions

message - this client received a message

{
    "action": "message",
    "message": <A_MSG>,
    "from": <SENDER_ID>
}

answer - received when someone answered to a message

{
    "action": "answer",
    "message": <A_MSG>,
    "from": <ANSWER_SENDER_ID>
}

registered - received when the server has successfully registered this client

{
    "action": "registered",
    "id": <AN_ID>
}

unregistered - received when the server has successfully unregistered this client

{
    "action": "unregistered",
    "id": <AN_ID>
}