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

amqp-swarm-graph

v0.1.3

Published

Node-to-node graph connections for amqp-swarm

Downloads

1

Readme

Node-to-node graph connections for amqp-swarm.

Usage

// earlier in the script
const amqpSwarmGraph = require('amqp-swarm-graph')

// called every time amqp-swarm connects to a node
const onNodeFound = async (node) => {
  const graphNode = amqpSwarmGraph(node)

  // attaching handlers
  graphNode.on('connect', (ctx, data) => data === 'alohomora')
  graphNode.on('disconnect', (ctx, data) => data === 'severus please')

  // attaching event listeners
  graphNode.events.on('connect',
    (remoteId) => console.log(`${remoteId} connected`)
  )

  // connecting to another node
  const connected = await graphNode.connect('remote-id', {some: 'data'})
  if (connected) console.log('connection successful')

  // accessing state
  graphNode.states['remote-id'].wololo = true

  // disconnecting
  const disconnected = await graphNode.disconnect('remote-id', 'goodbye')
  if (!disconnected) {
    console.log('oh come on')
    graphNode.forceDisconnect('remote-id')
  }
}

amqp-swarm-graph operates over amqp-swarm nodes, allowing them to connect in a graph pattern with each other. It automatically pings connected nodes, enables connect and disconnect filters, and tracks a state value associated with the connection.

Connections

Connection filters can be used to allow or deny connections based on data passed to them. The use case for this is business logic rather than authentication since all nodes run on server anyway, but if you feel like authentication is more relevant on the receiving side you can put it here too.

All connection filters take the following form:

async (ctx, ...args) => accepted

The result is a boolean, if true, allows the operation to proceed. They can be placed on the connect and disconnect events like amqp-swarm handlers:

graphNode.on(event, handler)

ctx has the result and throw properties, mirroring amqp-swarm. It also has the remote and state properties, which provide the involved remote's ID and a reference to the connection state, respectively, enabling filters to manipulate the state immediately.

By default, if no connection filters are attached, all operations go through.

Connection operations can be initiated using the following methods:

  • async graphNode.connect(remoteId, ...args): connects to a remote node, triggering its connect filters and passing ...args
  • async graphNode.disconnect(remoteId, ...args): disconnects from a remote node, triggering its disconnect filters and passing ...args
  • graphNode.forceDisconnect(remoteId): immediately disconnects remoteId

graphNode.events is an EventEmitter that receives the connect and disconnect events after a node has been connected or disconnected (including forceful disconnections). A string is passed to the event listeners, containing the involved remote's id.

Connection state

graphNode has two getters, connections and states. connections is simply a list of the connected remote node IDs, while states is an object, where keys are remote IDs and the values are the actual state objects.

The purpose of the state is to store any value relevant to the connection. It is initialized to an empty object and it's deleted if the remote is disconnected.

Contributing

Pull requests are welcome. As always, be respectful towards each other and maybe run or create tests, as appropriate. It's on npm test, as usual.

amqp-swarm-graph is available under the MIT license.