fiber_connection_pool 0.2.1 → 0.2.2

data/README.md

@@ -111,17 +111,28 @@ You have to be aware that the connection instance will remain in the pool, and o
 will surely use it. If the Exception you rescued indicates that the connection should be
 recreated or treated somehow, there's a way to access that particular connection:
 
+```  ruby
+pool = FiberConnectionPool.new(:size => 5){ MyFancyConnection.new }
+
+# state which exceptions will need treatment
+pool.treated_exceptions = [ BadQueryMadeMeWorse ]
+```
+
 ``` ruby
 begin
 
   pool.bad_query('will make me worse')
 
-rescue BadQueryMadeMeWorse
+rescue BadQueryMadeMeWorse  # rescue and treat only classes on 'treated_exceptions'
 
   pool.with_failed_connection do |connection|
     puts "Replacing #{connection.inspect} with a new one!"
     MyFancyConnection.new
   end
+  
+rescue Exception => ex  # do not treat the rest of exceptions
+
+  log ex.to_s  # -> 'You have a typo on your sql...'
 
 end
 ```
@@ -130,12 +141,16 @@ The pool saves the connection when it raises an exception on a fiber, and with `
 you execute a block of code over it. It must return a connection instance, and it will be put inside the pool
 in place of the failed one. It can be the same instance after being fixed, or maybe a new one.
 The call to `with_failed_connection` must be made from the very same
-fiber that raised the exception.
+fiber that raised the exception. The failed connection will be kept out of the pool,
+and reserved for treatment, only if the exception is one of the given in `treated_exceptions`. 
+Otherwise `with_failed_connection` will raise `NoReservedConnection`. 
 
 Also the reference to the failed connection will be lost after any method execution from that
-fiber. So you must call `with_failed_connection` before any other method that may acquire a new instance from the pool.
+fiber. So you must call `with_failed_connection` before any other method that may acquire a new 
+instance from the pool.
 
-Any reference to a failed connection is released when the fiber is dead, but as you must access it from the fiber itself, worry should not.
+Any reference to a failed connection is released when the fiber is dead, but as you must access 
+it from the fiber itself, worry should not.
 
 Save data
 -------------------

data/lib/fiber_connection_pool.rb

@@ -2,7 +2,7 @@ require 'fiber'
 require_relative 'fiber_connection_pool/exceptions'
 
 class FiberConnectionPool
-  VERSION = '0.2.1'
+  VERSION = '0.2.2'
 
   RESERVED_TTL_SECS = 30 # reserved cleanup trigger
   SAVED_DATA_TTL_SECS = 30 # saved_data cleanup trigger
@@ -194,6 +194,7 @@ class FiberConnectionPool
   # If no connection is available, yield the given fiber on the pending array
   #
   def acquire(fiber)
+    return @reserved[fiber] if @reserved[fiber] # already reserved? then use it
     if conn = @available.pop
       @reserved[fiber] = conn
       conn

metadata

@@ -1,7 +1,8 @@
 --- !ruby/object:Gem::Specification
 name: fiber_connection_pool
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.2
+  prerelease: 
 platform: ruby
 authors:
 - Ruben Caro
@@ -9,40 +10,43 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-09-02 00:00:00.000000000 Z
+date: 2013-09-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement
+    none: false
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
+    none: false
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
+    none: false
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
+    none: false
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
-description: |-
-  Fiber-based generic connection pool for Ruby, allowing
-                    non-blocking IO behaviour on the same thread
-                    as provided by EventMachine or Celluloid.
+description: ! "Fiber-based generic connection pool for Ruby, allowing\n                  non-blocking
+  IO behaviour on the same thread\n                  as provided by EventMachine or
+  Celluloid."
 email:
 - ruben.caro@lanuez.org
 executables: []
@@ -69,26 +73,27 @@ files:
 homepage: https://github.com/rubencaro/fiber_connection_pool
 licenses:
 - GPLv3
-metadata: {}
 post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
   requirements:
-  - - '>='
+  - - ! '>='
     - !ruby/object:Gem::Version
       version: 1.9.2
 required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
   requirements:
-  - - '>='
+  - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.6
+rubygems_version: 1.8.25
 signing_key: 
-specification_version: 4
+specification_version: 3
 summary: Fiber-based generic connection pool for Ruby
 test_files:
 - test/fiber_connection_pool_test.rb

checksums.yaml

@@ -1,7 +0,0 @@
----
-SHA1:
-  metadata.gz: 9fdb88ab21985a6014912366f1a917da8d0df76c
-  data.tar.gz: cc131028a049c18efc0029e63e83966b24cc10b0
-SHA512:
-  metadata.gz: 84abe69a34155bdf1307987d93a4b3c55cd0483be1d55ca0b50fadd8faf42f2582c46a1cada282beb9d245138c71829b00f3e86b8721a553ac75f6c8d1a9e414
-  data.tar.gz: d7f20e3e765f1e334405b0c333c86d63302804318856d2928823f9e10a00dc3015abfb826ccc773e39ab089621d958601301596564d062cfb7162cab7cc9bd3e