msgpp

C++ Lightweight Message Passing Interface

Installation

git clone https://github.com/cripplet/msgpp.git
cd msgpp
git submodule update --init --recursive
make test

Updating

git pull
git submodule foreach --recursive git checkout master
git submodule foreach --recursive git pull

Example

A working example can be found in tutorial/ -- the Makefile contained should compile as-is.

cd tutorial/
make

Replace the tutorial/external/msgpp symbolic link with a git clone of the msgpp repo will make tutorial/ a standalone project -- this is the preferred method for initializing new repositories with msgpp.

/**
 * example usage
 */

// init two nodes with IPv6 support and with timeout of two seconds
auto s = std::shared_ptr<msgpp::MessageNode> (new msgpp::MessageNode(8088, msgpp::MessageNode::ipv6, 2));
auto c = std::shared_ptr<msgpp::MessageNode> (new msgpp::MessageNode(8090, msgpp::MessageNode::ipv6, 2));

// allow 's' to receive messages
auto ts = std::thread(&msgpp::MessageNode::up, &*s);

// send a message "foo" to 's'
c->push("foo", "localhost", s->get_port());

// get the oldest (FIFO) message sent to 's'
std::string resp = s->pull();

// allow 'c' to also recieve messages
auto tc = std::thread(&msgpp::MessageNode::up, &*t);

// send a response to 'c' from 's' -- the last argument 'true' allows MessageNode::push to return
//	without throwing an exception in the case the message was not delivered
s->push("foo-resp", "127.0.0.1", c->get_port(), true);

// get the oldest message sent to 'c'
//	first argument is a hostname / ip filter (i.e. "127.0.0.1" and "localhost"), and
//	the second indicates MessageNode::pull should fail silently and return without throwing
//	an exception in case a message is not found
resp = c->pull("", true);

// shut down all servers within this process
raise(SIGINT);

ts.join();
tc.join();

Features

• IPv4 and IPv6 support -- talk to nodes halfway around the world in the same manner as talking to nodes in the local network
• simple protocol to emulate -- LEN:MSG messages sent through the default C socket interface (no need to worry about buffer parsing, etc.)
• atomic messages -- either the message is delivered in whole or dropped by the receiving node

Contact

• github
• gmail
• issues and feature requests should be directed to the the project issues page