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

pull-ping

v2.0.3

Published

measure latency/rtt and clock skew with pull-streams

Downloads

368

Readme

pull-ping

have a server and a client ping/pong each other

the server and client are symmetrical. first the client pings the server, then the server pings the client. this means both can measure keep the connection alive, and clock skew correctly, which is sure to be useful at some point.


var ping = require('pull-ping-pong')
var toPull = require('stream-to-pull-stream')

net.createServer(function (stream) {
  stream = toPull.duplex(stream)
  pull(
    stream,
    ping({timeout: 10e3}), //ping every 10 seconds
    stream
  )
}).listen(1234, function () {

  var stream = toPull.duplex(net.connect(1234))

  pull(
    stream,
    //ping every 10 seconds, set 'serve' to true to begin the ping.
    ping({timeout: 10e3, serve: true}),
    stream
  )

  setInterval(function () {
    //check rtt and skew to get statistics about the connection
    console.log(stream.rtt.mean, stream.skew.mean)
  }, 1000)

})

api

ping({timeout: ms, serve: boolean}) => Duplex pull-stream

timeout is the number of milliseconds. the default is 5 minutes, although the first ping will happen immediately.

set serve to true on one side of connection, this starts the ping pong. "serve" is ment in the (table) tennis sense, I set it on the client.

stream.rtt, stream.skew

Statistics on the round trip time and clock skew will be set on the stream object. These are instances of statistics

License

MIT