Socket
Socket
Sign inDemoInstall

grain-rpc

Package Overview
Dependencies
2
Maintainers
3
Versions
7
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    grain-rpc

Typed RPC interface on top of an arbitrary communication channel


Version published
Weekly downloads
143
decreased by-2.05%
Maintainers
3
Install size
160 kB
Created
Weekly downloads
 

Readme

Source

Build Status

layer a remote-procedure-call interface on top of simple messaging, using promises

You provide messaging between two endpoints, and in return you get the ability to register interfaces or functions at either endpoint, and call them from the other side.

All you need to do is:

  1. Provide a sendMessage() function to deliver messages to the other side.
  2. Call receiveMessage() whenever a message is received.

What you get is the ability to register entire interfaces (type-checked or unchecked) on either side, and call methods on those interfaces from the other side. This is particularly pleasant with typescript. For example, if you define this interface:

export interface ICalc {
  add(x: number, y: number): number;
}

Then on one side you can do:

import {ICalc} from './ICalc';
import {Rpc} from 'grain-rpc';

class Calc implements ICalc {
  public add(x: number, y: number): number {
    return x + y;
  }
}

const rpc = new Rpc({sendMessage: yourSendMessageFunction});
// ... hook up incoming messages to rpc.receiveMessage() ...
rpc.registerImpl<ICalc>("calc", new Calc());

And on the other side you can do:

import {ICalc} from './ICalc';
import {Rpc} from 'grain-rpc';

const rpc = new Rpc({sendMessage: yourSendMessageFunction});
// ... hook up incoming messages to rpc.receiveMessage() ...
rpc.getStub<ICalc>("calc");
console.log(await stub.add(4, 5));   // should print 9

Rpc library supports ts-interface-checker descriptors for the interfaces, to allow validation.

The string name used to register and use an implementation allows for the same Rpc object to be used to expose multiple interfaces, or different implementations of the same interface.

Rpc also supports a messaging interface, with postMessage() to send arbitrary messages, and an EventEmitter interface for "message" events to receive them, e.g. on("message", ...). So if you need to multiplex non-Rpc messages over the same channel, Rpc class does it for you.

Forwarding

Rpc connections can be linked together transparently using named forwarders. For example:

const frontend = new Rpc(...);
const backend = new Rpc(...);
frontend.registerForwarder("backend", backend);
frontend.getStub<ICalc>("calc@backend");
console.log(await stub.add(4, 5));   // will call calc.add(4, 5) on backend

Keywords

FAQs

Last updated on 08 Oct 2021

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc