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

remote-procedure-call-stream

v1.1.0

Published

Binary RPC protocol stream

Downloads

9

Readme

remote-procedure-call-stream

Binary RPC protocol stream.

npm install remote-procedure-call-stream

Usage

Client and server example.

The invoke methods takes three arguments, the remote method name, an array of arguments and an optional callback which is called with the return value from the server. If the callback is omitted the server will not send a response, this can be used for fire-and-forget type events.

var rpc = require('remote-procedure-call-stream')

var client = rpc.client()

// Pipe into a duplex stream, e.g. TCP socket
client.pipe(stream).pipe(client)

client.invoke('example', ['hello'], function (err, response) {
  console.log(response) // Prints 'world'
})

The server constructor accepts a handler function, it's always called with all three arguments, but the callback has no effect if the client didn't provide a callback function.

If the first argument passed to the callback function is an error instance the client will receive a corresponding instance.

var rpc = require('remote-procedure-call-stream')

var server = rpc.server(function (name, args, cb) {
  console.log(name) // Prints 'example'
  console.log(args) // Prints ['hello']
  cb(null, 'world')
})

server.pipe(stream).pipe(server)

Remote events

If you want the server to send data to the client without the client calling a function with a callback, you can use remote events. You can emit them like this from the server.

server.emitRemoteEvent({some: 'data'})

and then catch them like this on the client.

client.on('remote-event', function(data) {
  console.log(data) // {some: 'data'}
})