Version: 0.3.1-1-g192527c
Authors: erlanger.
This application implements a simple cluster-wide message broadcasting/listening library.
Version 0.3 includes the get_pid function.
It is meant to be a specific type of publish/subscribe model adapted to erlang's messaging and node structure.
key is any erlang term() that identifies
a desire to listen to messages. In the case ofget_pid(...) it identifies a server
that has been registered {via,grpoc,{n,l,Key}}. A cluster is defined as all the nodes connected to
the current node. In order to have a dynamic cluster,
where nodes can be automatically discovered you can usenodefinder at http://github.com/erlanger/nodefinder
to enable automatic discovery of nodes. It is very easy,
just include the nodefinder app in your release, and
it's done. No code to write.
nodefinder a cluster is dynamically managed
and all nodes on the LAN having the same erlang cookie and runningnodefinder are automatically added so that btune is always
connected to all the nodes.-
Project's repository:
https://github.com/erlanger/btune -
Git clone command:
git clone https://github.com/erlanger/btune.git
-
Simple API
-
It is based on gproc, so its foundation is solid.
-
Broadcast messages cluster-wide without having to know about Pids.
-
Listen to messages without having to know about registered servers.
-
Match keys with a pattern similar to ets:match().
Click on the btune module below to get to the documentation.
| btune |