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

sendy-ws

v1.5.2

Published

The clients in these modules are broken up into two types, reliable and unreliable

Downloads

7

Readme

Messenger pipeline

The clients in these modules are broken up into two types, reliable and unreliable

Unreliable clients can fail to deliver messages, get disconnected, etc. When you say unreliable.send(msg), you will never know if it was delivered. These clients talk directly over an unreliable network: websockets, udp, etc.

Reliable clients have no concept of a network, but guarantee in-order delivery if plugged into an unreliable client. At the core of the reliable client pipeline is a delivery-mechanism-agnostic implementation of the UTP protocol.

In certain situations, you need to wrap each packet that travels across the network in a special envelope, in which case you have the design below.

Because the UTP protocol will break things up into messages,

The basic design:

top level (application layer)

var reliable = {} // one per sender/recipient pair

// these can vary var unreliable = new Client({ url: '/some/websocket/url' }) (knows nothing of recipients)

// these guys don't know about unreliable // just a msg pipeline reliable[to].send(msg) // e.g. @tradle/otr-client -> sendy.send(msg) // length-prefix (@tradle/sendy) ('send', piece) // utp (break up into pieces) <- // bubble <- // bubble ('send', msg, to)

// we know who it's for because all those intermediates // are per-recipient

msg = wrap(msg) // wrap in to/from envelope u.send(msg)

u.on 'message' msg = unpack(msg) // unwrap envelope -> clients[msg.from].receive(msg.data) // bubble -> sendy.receive(msg) // bubble ('receive', msg) // piece-together, emit <- // length-prefix <- // otr client msg