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

rpc-amqp

v0.2.20

Published

node.js library for cross-application communication via amqp.

Downloads

32

Readme

rpc-amqp

node.js library for cross-application communication via amqp.

#Setup

Install the dependency:

npm install rpc-amqp

Require it in your application:

var RPC = require('rpc-amqp');

#Usage

To make the library working you need to have a default installation of RabbitMQ message broker: https://www.rabbitmq.com/download.html

##Client

Create a client object to send and receive RPCs (multiple objects could be created within the same scope):

var client = RPC.create();

##Connection

You can establish a connection to a default localhost with guest:guest credentials:

client.connect();

Or customize your connection with parameters:

client.connect({
    host: 'localhost',
    port: 5672,
    username: 'guest',
    password: 'guest'
});

##Ready

When the library connects to the broker and makes all preparations it emits ready event. At this point you can start registering callbacks and send RPCs:

client.on('ready', function() {
    // messages sending and callbacks registration here
});

##Workflow

The workflow consists of sending, receiving and returning the result:

  • to send a call you invoke call method on your client.
  • to receive a call you implement a callback function with client's register.
  • to return a result you pass a result object to callback function in register.

###client.call(name[,params][,options][,callback])

Makes a call with specified params and options. If there is a callback registered in the system the callback with a result will be returned.

  • name: name of the call that should be invoked remotely.
  • params: parameters of the call that will be passed to the remote consumer.
  • options: options that define the behaviour (like roles and routes) of the call. Allow to customize the call and
  • callback: callback function that will be invoked when the remote consumer replies with a result.

Here is an example of client.call usage:

sender.call('getRandomNumber', {}, {}, function(result){
    console.log(result);
});

###client.register(name[, callback])

Registers an RPC by a specified name. You can return a result object to the sender by calling callback.

  • name: name of the call that the client should reply to.
  • callback: function that could be called in if you want to reply with a result.

Here is an example of client.register that can listen to the call sent in the previous example (getRandomNumber):

client.register('getRandomNumber', function (params, response) {
    var number = Math.random();

    response(number);
});

#Routing

##Path

##ID

##Roles

#Examples

01 Basic - Random Number

02 Roles - Multiple Servers