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

ws-multi-proxy

v0.2.0

Published

Many to many WebSocket proxy server with pluggable routing logic. e.g. Take a bunch of existing WebSocket servers that only accept a single client connection and allow it to be used with multiple clients at once.

Downloads

2

Readme

ws-multi-proxy

Many to many WebSocket proxy server

There are some WebSocket servers that only support a single connected client at a time.
You may want to connect multiple clients to that same server.
This lets you do that.

Usage

  1. Setup a proxy server var proxy = new WebSocketProxy({ debug:true, webSocketServer:{ port:1234 } })
  2. Open http://www.websocket.org/echo.html in your browser
  3. Try it out using ws://localhost:1234/proxy/ws://echo.websocket.org

Advanced Usage

ws-multi-proxy is pretty simple wrapper around the ws module's WebSocketServer.

WebSocket connections are just http GET requests sent with some special headers. So, in order to accept WebSocket connections, we need an http server. The WebSocketServer can create one for you or use an existing http server instance if you have one.

Create a new http server

Or using an existing server instance you have lying around

var httpServer = require('http').createServer().listen(1234)

Create a WebSocketServer config

Tell it which server to use

var wssConfig = { server:httpServer }

Create a WebSocketProxy

Tell it which WebSocketServer config to use

var proxy = new WebSocketProxy({ webSocketServer:wssConfig })

Customize the routing logic

By default the mutateDataFrom* methods handle multiple clients by namespacing the message id. You can modify this logic to do whatever you want.

proxy.mutateDataFromServer =
proxy.mutateDataFromClient = function(data, sender, receiver){
  
  // perform some sort of custom message validation
  if (data.myCustomToken != receiver.myCustomToken)
    return false // don't sent message
  
  // or maybe augment the message before it is received
  data.value += " lol, augmented value"
  
  return data
}

Or keep the existing functionality by monkeypatching.

var oldMutateDataFromClient = proxy.mutateDataFromClient
proxy.mutateDataFromClient = function(data, sender, receiver){
  
  // some sort of custom message validation
  if (data.myCustomToken != receiver.myCustomToken)
    return false // don't sent message
  
  return oldMutateDataFromClient.call(this, data, sender, receiver)
}