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

node-orleans

v0.0.1

Published

A node.js client for Codename Orleans

Downloads

5

Readme

node-orleans

A node.js client for Codename Orleans.

Installation

Install the module with npm:

$ npm install node-orleans

Ensure the following are in the same directory as your node.js application:

  • Orleans.dll
  • Microsoft.WindowsAzure.StorageClient.dll
  • Your grain interfaces.dll
  • ClientConfiguration.xml

Initialising the client

First you need to initialise the client:

var orleans = require('node-orleans');
var client = orleans({
	grainDll : "MyGrainInterfaces.dll", 	// the assembly containing your grain interfaces
	grainNamespace : "MyGrainInterfaces"	// the namespace of your grain interfaces
});

client.init(function(err){
	if (err) console.log(err);
	// we are ready to go!
});

Calling a grain

The client has a call function which allows you to send a message to a grain:

client.call(grainType, grainId, grainMethod, arguments, callback)
  • grainType The name of your grain interface without the I (i.e. 'Grain1')
  • grainId The ID of a grain. This can be either an integer, string (which will be parsed as a guid) or an array with an extended primary key [integer/string, string]
  • grainMethod The name of the method you want to call
  • arguments An array of arguments
  • callback A function which will be called back on completion of the request. For grains with no return value (i.e. they return Task) this should be function(err), otherwise this should be function(err, result)

So for a grain interface that looks like this:

namespace MyGrainInterfaces
{
    public interface IGrain1 : Orleans.IGrain
    {
        Task SetValues(string stringValue, int intValue, bool boolValue);
        Task<string> GetString();
    }
}

We would use the following code to call it from node:

// IGrain1.SetValues
client.call('Grain1', 0, 'SetValues', ['myString', 100, true], function(err){
	if (err) console.log(err);
});

// IGrain1.GetString
client.call('Grain1', 0, 'GetString', [], function(err, result){
	if (err) console.log(err);

	console.log(result); // 'myString'
});

Known Issues

  • Grains with generics are not supported (i.e. IGrain<T>)
  • Only simple types are supported (i.e. string, int, double, bool );

License

MIT