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

ll-protocol

v1.0.1

Published

Custom TCP protocol

Downloads

7

Readme

ll-protocol

Node.js custom TCP protocol

Characteristics

  • Send multiple messages at the same time on the same socket
  • listen to a type of message by adding a event listener
  • Allow streaming of messages
  • Message body can be raw bytes
  • protocol is written with es2015 (es6) syntax

Usage

Server

const net = require("net");
const fs = require("fs");
const LLProtocol = require("ll-protocol");

server = new net.Server();

server.on("connection", (socket) => {
    let protocol = new LLProtocol(socket);

    // accept a file
    protocol.on("someFile", (request) => {
    	const filename = request.headers.filename;

    	const writer = fs.createWriteStream(filename);

    	request.pipe(writer);
    });


    // send a basic string message ('makeResponse' already calls 'send' for response)
    const response = protocol.makeResponse('someMessage', 'This is some content to send');

});

server.listen(8000);

Client

const net = require("net");
const fs = require("fs");
const LLProtocol = require("ll-protocol");

const StringRequest = LLProtocol.request.StringRequest;

const client = new net.Socket();

client.connect(8000, () => {
    const protocol = new LLProtocol(client);

    // accept a basic string message
    protocol.setReader('someMessage', StringRequest);

    protocol.on("someMessage", (content) => {
    	console.log("someMessage event fired with content:", content);
    });


    // Send a file
    const filename = "thisissomecoolfilename.txt";
    const reader = fs.createReadStream(filename);

    const response = new LLProtocol.Response({ type: 'someFile', filename });

    reader.pipe(response);

    protocol.send(response);

});

Protocol

Message

---------------------------
|      Header (json)      |
| { type: 'messageType' } |
---------------------------
|      HEADERSEQUENCE     |
---------------------------
|      Message Content    |
|      (raw bytes)        |
---------------------------

Frame

When a message is streamed to the protocol, all chunks get into its own frame. A frameheader and frame sequence are added to the frame.

---------------------------
|  Frameheader (9 bytes)  |
---------------------------
|      Frame Content      |
|      (raw bytes)        |
---------------------------
|      FRAMESEQUENCE      |
---------------------------

Frameheader

------------------------------
|    Message Id (4 bytes)    |
------------------------------
|    Frame index (4 bytes)   |
------------------------------
| Last frame (bool) (1 byte) |
------------------------------

HEADERSEQUENCE and FRAMESEQUENCE

The sequences are both an array of bytes. The numbers are a decimal representation of the byte value (min: 0, max 255)

LLProtocol.config.SEQUENCES.header = [ 0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 0 ];
LLProtocol.config.SEQUENCES.frame = [ 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1 ];

Because the sequences are the same for 10 bytes, when going through the chunks, it only need to check once every 10 bytes. This makes it a lot faster.