Test case for #55, is passing.
Proper failing test case for #55

1) The API sends a Content-Type: application/json body with no header.

2) The response handler in faraday tries to parse the body response for a HEAD
request.

Time to compensate.
Error parser checks body even with JSON type
Merge branch 'mattly/55-client-ping-raises-correctly-on-error'
bump to 0.6.3, release notes
[#37] Switch default adapter: net-http-persistent

Sure, this ropes in another gem dependency, but it's a good one.  Also in my
very unscientific tests, it speeds up repeat access to the API by about 4x.
readme update on http default
[#65] failing test to reproduce problem
[#65] Handle non-synchronous responses correctly
[#65] Parse JSON bodies of parallel responses

Can't use the Faraday-Middleware gem for this anymore, and it's meta-programmed
up enough that fixing it to support non-synchronous requests would be painful.
So, we do our own JSON rendering.
documentation fix
Merge branch 'mattly/65-parallelism'
Merge branch 'mattly/37-faraday-adapter'

Conflicts:
	orchestrate.gemspec
Orchestrate::Application constructor

baby steps
Orchestrate::Collection
Collection#destroy!
Collection#[]
KeyValue#load / #initialize WIP
Collection#[] returns nil on NotFound
KeyValue#[], #[]=