remove unnecessary config from copy/pasted gradle files
clojure build
first version of ws-client

Written in Clojure.
Sends requests against given server with defined number of threads (or defaults to number of processors)

      Example: (run-load-test "http://localhost:8888/ws-java-servlet-blocking/testA" 2)

Currently does not have a run script, only executable through Clojure REPL. A script or gradle task will come.

It outputs logs like this for now:

timestamp:1358790809982 threads: 2 duration: 362.656
timestamp:1358790810135 threads: 2 duration: 333.307
timestamp:1358790810316 threads: 2 duration: 333.771
timestamp:1358790810476 threads: 2 duration: 340.92
timestamp:1358790810659 threads: 2 duration: 342.781
timestamp:1358790810810 threads: 2 duration: 333.922
timestamp:1358790810941 threads: 2 duration: 281.883

This will evolve as I work on the tools to convert from logs across distributed clients into a single report with graphs.
exclude the Eclipse /bin/ folders.

If someone tries to add a real /bin/ folder with scripts they'll need to force it.
move response-log agent to locally bound var rather than namespaced

This allows multiple load tests to run if desired without stomping on a global var.
docs
include server_response_time
output log in JSON format for graph generation

- not yet capturing server_time correctly
- log file is still hardcoded

… and yes, I'm hand-writing JSON. I want it to write out (streaming) as data is available rather than generating a big object in memory and I didn't feel like using Jackson for such simple JSON.
log include server-time now
bug fixes in JSON and Clojure
Merge pull request #1 from NiteshKant/master

ws-impl-netty implementation
create a "fat jar" that is executable for the client
rename and main method implementation for executable jar
Merge branch 'ws-client'

Conflicts:
	ws-impls/ws-java-servlet-blocking/src/main/java/perf/test/TestCaseAServlet.java

For some reason most of these files … despite no conflicts needed to be manually merged and re-committed.
The TestCaseAServlet.java was a collision and needed to be manually merged.
System.exit after client finishes

… the thread/connection pools must be left and not closing so it won't shut down … instead of tracking them down right now I'm forcing it to exit.
new addResponseHeader utility method
script for running client and cleaned up console output
don't throttle per route
hardcode to python 2.7 for now as it's not working on machines with both 2.4 and 2.7 on them
script for monitoring network on linux