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

retransmitting-websocket

v1.0.0-alpha.0

Published

A generic higher level wrapper to ensure state is retransmitted after network failure

Downloads

10

Readme

Retransmitting-WebSocket

A tiny zero dependency wrapper around a WebSocket to ensure no messages are lost after a network failure. This is useful if you are dealing with a stateful/mutable protocol over network. Retransmitting-WebSocket ensures messages do not get lost nor are they sent or received multiple times. Retransmit also handles reconnecting for you.

This project was created for use in Greenfield

Usage

Both sides need to wrap their WebSocket in a RetransmittingWebSocket. This RetransmittingWebSocket is stateful so make sure that the same 2 are talking to each other on reconnect.

import ReconnectingWebSocket from 'reconnecting-websocket'
import { RetransmittingWebSocket } from 'retransmit.js'

// all options are optional
const retransmittingWebSocket = new RetransmittingWebSocket({
  maxUnacknowledgedBufferSizeBytes: 100000, // Maximum cummulative size of all received messages before we confirm reception.
  maxUnacknowledgedMessages: 100, // Maximum cardinal size of all received messages before we confirm reception.
  maxUnacknowledgedTimeMs: 10000, // Time after last messages before we confirm reception.
  closeTimeoutMs: 1500000, // Maximum time after network failure before we consider the connection closed.
  reconnectIntervalMs: 3000, // Reconnection interval. Time to wait in milliseconds before trying to reconnect.
  webSocketFactory: () => { new WebSocket(myURL) } // Function to use for creating a new web socket when reconnecting.
})

// No need to make ReconnectingWebSocket queue messages, RetransmittingWebSocket will take care of it.
retransmittingWebSocket.useWebSocket(new WebSocket('ws://my.site.com')) // .
//☝️ The used WebSocket can be swapped on the fly. This is required server-side so you can use a new incoming 
// WebSocket instance each time the old one is disconnected. The only requirement is that the other side keeps using the same 
// retransmittingWebSocket object.

retransmittingWebSocket.onmessage = (event) => {
  // Simply handle application payload here like you would with a normal WebSocket.
}


const somePayload = new Uint8Array([1,2,3,4])
retransmitter.send(somePayload) // retransmitter ensures the payload will be delivered exactly once, regardless of the connection state.