This directory contains the definition of the Chirp I/O protocol
and two examples of its use.

Chirp is a lightweight I/O protocol designed to bootstrap applications
into a grid computing environment.  The protocol itself is defined
in the file PROTOCOL.

Two client libraries, one in Java and one in C, are contained in this
directory.  These are intended to be taken by end users in source
form and incorporated into their programs.  

THESE LIBRARIES ARE COMPATIBLE WITH THE CHIP SUPPORT BUILT INTO
CONDOR VERSION 4.x.

Chirp is currently used between the Condor starter and a user's
job.  The job looks for a file named "chirp.config" in the execute
directory which contains the address of the starter's socket and
a cookie with which to authenticate.  It connects to that socket,
presents the cookie, and then performs I/O using Chirp requests.
The starter transforms these into remote I/O operations, using all
of the goodness of Condor's networking support (e.g. support for
encrypted sockets, authentication w/ Kerberos or X509, etc), and 
converts the responses back into Chirp.