EVPath

EVPath is taking applications for the position of "project logo".  Please Email your qualificiations...

EVpath is designed to be an event transport middleware layer. Specifically, it is designed to allow for the easy implementation of overlay networks, with active data processing, routing and management at all points in the overlay.

EVpath specifically does not encompass global overlay creation, management or destruction functions. Rather it focusses on providing efficient environment for routine transport, while providing interfaces necessary for external management layers.

The package is built around the concept of "stones" (like stepping stones) which are linked to build end-to-end "paths". While the "path" is not an explicitly supported construct in EVpath, the goal is to provide all the local, stone-level, support necessary to accomplish their setup, monitoring, management, modification and tear-down.

Stones in EVpath are lightweight entities that roughly correspond to processing points in dataflow diagrams. Stones of different types perform data filtering, data transformation, mux and demux of data as well as transmission of data between processes over network links.

To see EVPath as it is, please peruse the Doxygen-generated documentation.  It's as much of a manual as exists at this point.

Getting EVpath.

EVPATH is available under the new BSD license. EVPATH requires several packages from the Chaos repository at Georgia Tech: dill, cercs_env, gen_thread, atl, ffs, and evpath.

To download and install these libraries, a script (trunk/chaos_build.pl) is available at: http://svn.research.cc.gatech.edu/kaos/chaos_base/ (username: anon, password: anon).

Download the chaos_base repository using SVN, and follow the instructions at the top of the script. You can also download a source tarball directly. Alternatively, for binary installations we have :

Be aware that you need to customize the /usr/local/lib/cercs_config (or ${HOME}/cercs_config) file to reflect your systems configuration if you use it on a non CoC machine.

However, if you're going to be making changes, porting to a new platform or doing anything else that may require closer ties to our source trees, please consider asking for non-anonymous SVN accesst for relevant packages.



This page is maintained by  Greg Eisenhauer