HTTP persistent connection support for ActiveResource.
Tested with ActiveResource:
Add this line to your application's Gemfile:
gem 'activeresource-persistent', :require => 'active_resource/persistent'
And then execute:
Or install it yourself as:
$ gem install activeresource-persistent
Works out of box after adding:
Supported ActiveResource ssl options:
Unsupported ActiveResource ssl options:
Currently we use passenger server because it provides REMOTE_PORT enviroment variable. Thus we can ensure that connections are persistent.
Before start suite ensure that passenger gem are installed correctly.
$ BUNDLE_GEMFILE=Gemfile_3.2.9 bundle $ BUNDLE_GEMFILE=Gemfile_3.2.9 bundle exec passenger start
Run tests with:
$ BUNDLE_GEMFILE=Gemfile_3.2.9 bundle $ BUNDLE_GEMFILE=Gemfile_3.2.9 bundle exec rspec -fs -c spec $ rake test:gemfile_2.3.10 # Testing with Gemfile_2.3.10 $ rake test:gemfile_3.0.10 # Testing with Gemfile_3.0.10 $ rake test:gemfile_3.1.4 # Testing with Gemfile_3.1.4 $ rake test:gemfile_3.2.3 # Testing with Gemfile_3.2.3 $ rake test:gemfile_3.2.9 # Testing with Gemfile_3.2.9
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Added some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request