Since the usual pattern is that a page gets rerendered after failure, the proper behavior would be to set the flash directly, so that it doesn't stick around if you give up and leave the page.
This will enable easier testing against various versions of dependencies.
include explicit Gemfile step in readme
HttpCacheResponder returns 304 even when the collection has different set of resources
…tion has different set of resources'. Last-Modified header will not be set for GET on Collection
…304 even when collection has changed
config.generators in Rails::Railtie is deprecated. But, we should keep it for Rails 3.0.x.
…collection path (index action) after POST/PUT/DELETE.