Oh no, another breaking change! Didn't we just have one of these? Move fast and break things, right?
In the spirit of Mike Perham's latest blog post, "Kill Your Dependencies," I've decided to remove Dalli::RateLimiter's dependency on the connection_pool gem. Let me be crystal clear that Dalli::RateLimiter is still 100% usable with connection_pool, you'll just have to add the gem to your project and create the instance yourself if you want to use it. It was barely even a code change (seriously, take a look at the diff).
This is the only significant change of this release. Even the benchmarking results I posted about in the v0.2.0 release and README still stand. Again, if you want to use a ConnectionPool, just 1. add connection_pool to your Gemfile, 2. instantiate it (e.g. $dalli = ConnectionPool.new { Dalli::Client.new }), and 3. pass it to Dalli::RateLimiter.new as the first argument. That's it!
Hopefully this will slim down folks' bundles and help them be more aware of the gems they're actually using.