nrtb-core team mailing list archive

Thread
Date

[Question #147131]: Is MUSCLE appropriate to use as our communications engine.

To: nrtb-core@xxxxxxxxxxxxxxxxxxx
From: Rick Stovall <question147131@xxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 27 Feb 2011 19:07:23 -0000
Reply-to: question147131@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

New question #147131 on New Real Time Battle:
https://answers.launchpad.net/nrtb/+question/147131

Rather than rolling our own IPC layer, I'm thinking it may be advantageous to use this pre-rolled system Any thoughts? 

https://public.msli.com/lcs/muscle/index.html

The MUSCLE system is a robust, somewhat scalable, cross-platform client-server solution for dynamic distributed applications for Linux, BSD, Windows, MacOS/X, and other operating systems. It allows (n) client programs (each of which may be running on a separate computer and/or under a different OS) to communicate with each other in a many-to-many message-passing style. It employs a central server to which client programs may connect or disconnect at any time (This design is similar to other client-server systems such as Quake servers, IRC servers, and Napster servers, but more general in application). In addition to the client-server system, MUSCLE contains classes to support peer-to-peer message streaming connections, as well as some handy miscellaneous utility classes. As distributed, the server side of the software is ready to compile and run, but to do much with it you'll want to write your own client software. Example client software can be found in the "test" subdirectory.

-- 
You received this question notification because you are a member of NRTB
Core, which is an answer contact for New Real Time Battle.