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

agnostic-rpc

v1.2.1

Published

RPC handler for any type of transport

Downloads

11

Readme

Agnostic RPC

Attach an ID to remote procedure call to return results to the function that requested them. Useful, for example, when transmitting multiple requests and responses to a remote server over websockets, where the responses may come back out of order.

Quick Start

Single request, single response, with Promise

const rpcServer = new AgnosticRpcServer();
const rpcClient = new AgnosticRpcClient();

rpcServer.on('request', function({request, options, respond}) {
	// Server logic goes here
	respond('response-message');
});

rpcServer.on('response', function(response) {
	let encodedResponse = response.encoded;
	// Transmission of encoded response from server to client goes here
	// In this example, they're directly connected
	rpcClient.handleResponse(encodedResponse);
});

rpcClient.on('request', function(request) {
	let requestEncoded = request.encoded;
	// Transmission of encoded request from client to server goes here
	// In this example, they're directly connected
	rpcServer.handleRequest(requestEncoded);
});

rpcClient.request('request-message')
	.then(function(response) {
		// Response should equal 'response-message'

	});

Single request, multiple responses, with Promise

const rpcServer = new AgnosticRpcServer();
const rpcClient = new AgnosticRpcClient();

rpcServer.on('request', function({request, options, respond, cancel}) {
	// Server logic goes here
	respond('response-message-1');
	respond('response-message-2');
	cancel(); // Cancel after two responses sent
});

rpcServer.on('response', function(response) {
	let encodedResponse = response.encoded;
	// Transmission of encoded response from server to client goes here
	// In this example, they're directly connected
	rpcClient.handleResponse(encodedResponse);
});

rpcClient.on('request', function(request) {
	let requestEncoded = request.encoded;
	// Transmission of encoded request from client to server goes here
	// In this example, they're directly connected
	rpcServer.handleRequest(requestEncoded);
});

rpcClient.request('request-message', {
	multipleResponses: true
}, function(response) {
	// First response should equal 'response-message-1'
	// Second response should equal 'response-message-2'
})
.then(function(response) {
	// This will not execute until the request is canceled
});

Single request, multiple responses, with controller

const rpcServer = new AgnosticRpcServer();
const rpcClient = new AgnosticRpcClient();

rpcServer.on('request', function({request, options, respond}) {
	// Server logic goes here
	respond('response-message-1');
	respond('response-message-2');
	respond('response-message-last');
});

rpcServer.on('response', function(response) {
	let encodedResponse = response.encoded;
	// Transmission of encoded response from server to client goes here
	// In this example, they're directly connected
	rpcClient.handleResponse(encodedResponse);
});

rpcClient.on('request', function(request) {
	let requestEncoded = request.encoded;
	// Transmission of encoded request from client to server goes here
	// In this example, they're directly connected
	rpcServer.handleRequest(requestEncoded);
});

let rpcRequest = rpcClient.requestController({
	multipleResponses: true
});

rpcRequest.request('request-message');

rpcRequest.on('response', function(response) {
	// First response should equal 'response-message-1'
	// Second response should equal 'response-message-2'
	if(response === 'response-message-last')
		rpcRequest.cancel();
});

rpcRequest.on('end', function() {
	// Called right after cancel
});

Changes

  • v1.2.0: RPCServer's 'request' event now emits requestController with a cancel function

TODOs

  • Timeouts