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

moscow

v0.1.0

Published

Simple, reliable and well tested OSC servers and clients for node.js

Downloads

6

Readme

node-moscow

Build Status

node-moscow is a node package providing simple, reliable and well tested OSC servers and clients for node.js. It implements servers and clients for OSC communication on top of TCP and UDP.

To install it run npm install moscow

Minimalist example

server.js

// Creates a UDP server, listening on port 9000
var server = new require('moscow').createServer(9000, 'udp')

// Bind to the `message` event to handle incoming messages 
server.on('message', function(address, args) {
  console.log(address, args)
})

// Start the server
server.start(function() {
  console.log('server started')
})

client.js

// Creates a UDP client sending to host 'localhost' on port 9000
var client = new require('moscow').createClient('localhost', 9000, 'udp')

// Call the `send(address, args)` method to send a message
client.send('/bla/blo', [11, 22, 'hello'])

API

moscow

createClient(host, port, transport)

Create and return a new OSC client.

var udpClient = moscow.createClient('192.168.2.100', 9000, 'udp')
  , tcpClient = moscow.createClient('192.168.2.110', 9001, 'tcp')

createServer(port, transport)

Create and return a new OSC server.

var udpServer = moscow.createServer(9000, 'udp')
  , tcpServer = moscow.createServer(9001, 'tcp')

Server(port)

Event: 'message'

Emitted when an OSC message was received by the server. Handlers are passed two arguments address, the OSC address, and args the list of arguments sent along the message. Example :

server.on('message', function(address, args) {
  if (address === '/color')
    console.log('R:' + args[0] + ',G:' + args[1] + ',B:' + args[2])
})

Event: 'error'

Emitted when an unexpected error happened.

Server.start(done)

Starts the server and calls done(err).

Server.stop(done)

Stops the server and calls done(err).

Client(host, port)

Event: 'error'

Emitted when an unexpected error happened.

Client.send(address, args)

Sends an OSC message to address with arguments args. Example :

client.send('/hello', ['max', new Buffer('sam'), 'john'])

FAQ

What is the difference between UDP and TCP?

UDP is the commonly used with OSC because it is faster than TCP. On the other hand, with UDP you might loose some messages, while TCP ensures all packets are properly received. So this is a trade-off to make, depending on your requirements.

Changelog

  • 0.1.0 Initial release: UDP, TCP client + server.