Use https rubygems source with bundler.
Fix bundler arguments syntax passed for CI.
remove RUBY_VERSION guard and prefer Gemfile platform's.
partial revert of last commit.

Bundler doesn't seem to be able to distinguish between jruby 18
and jruby 19. There's just "jruby". ruby_19 covers rubinius/MRI
only.

Still only building redcarpet on 1.9+ since it doesn't build on
1.8 anymore.
reel pulls in nio4r dependency for us.
Don't rely on Rack::Response for sanitizing response headers.

Rack::Response iterates over given body which in some cases,
like Fiber streaming, may block responding to client.
https://github.com/rack/rack/blob/master/lib/rack/response.rb#L35-L38

RackResponse is introduced instead to cleanup Content-Type header
in order to pass Rack::Lint.
Use reel on platform ruby_20 as well.

Conflicts:
	Gemfile
Also test ruby 2.0.0 on travis-ci.
Fix deprecation warning on ruby 2.0.

"Enumerator.new without a block is deprecated; use Object#to_enum"
Reel adapter fixups

This is a snapshot of the Reel adapter I'm using in the Cryptosphere.

It includes some general refactoring and the following notable changes:

* Support for mapping extended HTTP verbs to the _method pseudoparameter (e.g.
  for WebDAV support)
* Joins to the foreground actor rather than sleeping the thread. This fixes
  deadlock detection issues
* Streaming support: passes Reel's request.body objects through unmolested
  rather than using LazyRequestBody
Merge pull request #113 from seancribbs/reel-adapter-fixups

Reel adapter fixups
Lock Reel version to 0.3.0

Reel 0.4.0 contains breaking API changes. Locking to 0.3.0 will ensure
that the existing tests continue to pass until the adapter itself can be
updated to the new API.
Merge pull request #115 from seancribbs/lock-reel-version

Lock Reel version to 0.3.0