EPI framework

Introduction:

The intention of the library is to cover the holes that EI library offers:

• An object oriented implementation
• A simple API
• Extensibility
• Abstraction of comunication mechanism
• Simplified management of incoming messages (mailboxes)

EPI is realased under the LGPL license. For details please see the file "COPYING" distributed with EPI source code.

EPI works in a similar manner than jinterface the library for java http://www.erlang.se/doc/doc-5.0.1/lib/jinterface-1.2/doc/.

It have some differences:

• All comunication is done throw MailBoxes, no matters if you use self or auto managed nodes.
• Epi abstracts the comunication mechanism, and you can extend it with new mechanism (using ErlangTransport interface and ErlangTransportFactory)

NOTE: EPI is a alpha version and is probably full of bugs.

Where can I get it?

EPI is hosted in sourceforge.net, at http://www.sourceforge.net/epi

Requirements:

In order to build EPI you need the following software:

• Scons (www.scons.org)
• g++ (tested with version 3.3)

And the following libraries:

• OpenThreads library. http://openthreads.sourceforge.net/

  I highly recomend get the sources from cvs:

  cvs -d :pserver:cvsguest@openscenegraph.org:/cvs/OpenThreads login cvs -d :pserver:cvsguest@openscenegraph.org:/cvs/OpenThreads co OpenThreadsUpdate

• LibCWD for debug messages. Not needed if debug is disabled. http://libcwd.sourceforge.net/ - EI library (tested with version 3.5)

Related links