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

tcp-ip-connman

v1.0.6

Published

Connection manager for tcp/ip connections

Downloads

11

Readme

NPM

Build Status codecov Dependency Status Code Climate Known Vulnerabilities Inline docs contributions welcome

What

tcp-ip-connman stands "tcp-ip Connection Manager". As the name says, it takes care of connections for you, with automatic reconnects, heartbeat and events, you don't need to worry if your connections are up or down, tcp-ip-connman will take care of that for you.

With tcp-ip-connman all you need to do is to connect, and forget all your problems!

Why

TCP/IP connections are tricky, mainly becasuse of half-closed and half-open connections.

While Node.js does a decent job dealing with half-closed connections, we can't say the same for half-open connections.

Basically, if the end of a connection dies, the other end will remain open, like nothing happened.

This library takes care of half-open connections, by implementing a heartbeat and by having a event rich API to let you know everything you need.

If you don't want to use the events API, that's fine as well, as tcp-ip-connman manages timeouts and connection drops automatically reconnecting for you.

How

Following are instructions on how to intsall and use tcp-ip-connman. For questions you can ask in the issues page:

Feel free to check the project's page for additional information on the API as well.

Install

npm install tcp-ip-connman --save

API

  • connect
  • disconnect
  • isConnected
  • send
  • onClose
  • onOpen
  • onRead
  • onRetry
  • setConnectFn

Examples

Creating a connection manager with a custom heartbeat and connect:

const connmanager = require("tcp-ip-connman");
const heartBeat = heartBeatFactory();
heartBeat.setPing("Marco");
heartBeat.setPong("Polo");
heartBeat.setBeatInterval(50);
heartBeat.setBeatTimeout(150);

const client = connmanager(heartBeat);

client.connect({host: "localhost", port: 8080})
    .then(() => console.log("success!")
    .catch(console.log);

Creating a connection manager with a default PING, PONG and heartbeat:

const connmanager = require("tcp-ip-connman");

//Default PING is Buffer.from([0x01])
//Default PONG is Buffer.from([0x02])
//Default TIMEOUT and INTERVAL are from heartbeatjs (https://www.npmjs.com/package/heartbeatjs)
const client = connmanager();

client.connect({host: "localhost", port: 8080})
    .then(() => console.log("success!")
    .catch(console.log);

Using a previously created connman to define behaviors for the various events:

client.onOpen(online => {
    console.log(`Connection established: ${online}`);
});

client.onClose(online => {
    console.log(`Connection established: ${online}`);
});

client.onRead(data => {
    console.log(`Data received: ${JSON.stringify(data)}`);
});

client.onRetry((error, num) => {
    console.log(`Retry number ${num} due to error ${JSON.stringify(error)}`);
});