Added benchmark for evhttp-sharp (libevent2-based simple web server)
undoing setup.py change, bigger db pool, fixed problem with mysql in pooling
Draft version of all tests
Changed formatting
Added /plaintext endpoint for Test 6
Refinements based on suggestions by Adam Chlipala
Added benchmarking periphera
Added README
Fixed README syntax
avoid an exception in the /db test where the ?queries= arg is missing.
generate the right json in both database tests.
fixed networking issue, added windows test case
removed typo from setup.py
type Html is now correctly deduced to text/html
Adds a configruation file option that can be overridden by command-line args

Note that this borrows very heavily from http://stackoverflow.com/a/5826167
Only a small portion of this is my own code
Improved path handing for config file
Update Spring sample application

Prior to this commit, the sample application used for Techempower
benchmarks was using spring-framework 3.2.1, manually managing
Hibernate sessions, and old app configuration.

This commit updates this sample application.
Spring projects were added/updated:
* Spring-Framework 4.0.0.RC1
* Spring Boot
* Spring Data JPA

Application layout was updated as well, using:
* Spring Boot App launcher
* Spring Data repositories
* Full Java Configuration
Simplified boot application
Rollback to a more optimal Spring Boot application

The application now run within an executable JAR
and uses Spring Boot's defaults for configuration.

Benchmark setup code and configuration have been updated to reflect those changes.
18938 Break logging into individual files

Previously, all "logging" was sent to standard out, and we would
capture that in a file. The problem with this is that all of the
frameworks would be logged to the same file, resulting in an
extremely large log.

This change causes each individual framework to create a log file
in the results folder, and captures the standard output there.
Additionally, each setup file now has start/stop functions that
require a 'logfile' argument. Initially, basically all of the tests
do not use this file, but this gives the possibility to attach
the logfile as the capture for stderr/stdout on the subprocesses
spawned when a server is spun up.

Similarly, 'logfile.write()' will allow a developer to enter logs
directly for debug or general purposes.
18938 Forcing stdout and stderr to the logfile

Each framework gets a logfile, and we want to make the noisier
tests write their output to their logfile rather than the system
stdout/stderr.