changed a typeo

Cleaned up some comments.

fixed typos in README and gave more complete descriptions

added MIT license to nearly every file and wrote up a nice state of the project synopsis in the README file

complete upgrade of connection pool w/integration into consumers; wrote backtest test1.cfg as a test harness. It will exhibits timing problems in the absence of output to stderr. At present its hanging. Lewis called a halt to the project. This is the last checking for a while, or ever

working threaded version of the backtester; still needs admin stuff to know when to quit, etc

version that do not drop messages 90% of the time

Check in of a working version of the backtester using the beanstalk server. The working version currently uses EM-Jack which uses EventMachine. Other clients exist and may be higher performance. The EM based client has some oddities: when run as a single process it generates 19K+ positions. When run with 4 forked child processes it generates over 41K. Since the positions table is has a primary key on entry_date and ticker_id, they can't be duplicate positions. THIS MUST BE INVESTIGATED!

commit before change to AMQP with Bunny client

changed db update routines to use forks instead of launching rake jobs

able to run backtests with icc compiled libs and many further optimizations

last commit before branching on eventmachine

runs a backtest correctly on several config files

fixed bug in remote logger that was allocation multiple DrbObject for the same log file. Uknown how this will work in the multi-process case where drb requests for a logger may come at the same time (no way to serialize...maybe Rinda will work for that

re-implemented the remote logger such that multiple loggers are managed and passed back to the client process