thread-inheritable_attributes 1.1.0.beta1 → 1.1.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 83c5bf46acdb7eece51054d9dbb2d2c8ba5a7cd3
4
- data.tar.gz: e1a1e6199bd7630e7ef75d2c35d005e8e0049366
3
+ metadata.gz: a3130d7814970966125c54e062264925dba75989
4
+ data.tar.gz: 030e341b1d316194ca55ce125b67b74ec94b9f85
5
5
  SHA512:
6
- metadata.gz: bfbd56fa3ae6f6ee3033cf2805a2a53f4d998bc208513e8d800da99a4de267e991dea72c70977e152e047f569b87963be85c00efaee180eaa2c4f271f563a239
7
- data.tar.gz: dbabee7900d20b1386106ecb4c62c351acae02dd60043a0d67ea042d21a2b302ae08df5c10d32e425c2a1c4d7eed6827759c42b1ad7f212778221a6d2457d9b6
6
+ metadata.gz: c10e9d1ff9977fbd4c97fb06557be98aa3b348377391e9175a2f99517ad5a389a109127406876a00739a46996bc7141dba8a55508d46e1d13bb588cd7ffe6868
7
+ data.tar.gz: ec351ce13c0974acd328993d799e27fbbe77843833104739d574ce1bf57cbdd78b26c2364bd69664cf7d2d1018288447a948de2a74431f3ae3d5b12e12c3f16c
data/CHANGELOG.md CHANGED
@@ -1,8 +1,12 @@
1
1
  ## v1.1.0.beta1 - 2016-06-14
2
2
 
3
3
  ### Fix
4
- Add request_store gem as an optional dependency for when working within the context of a multi-threaded web server.
5
- Addresses the use of `Thread.current` and replaces it with `RequestStore` when the gem can be required.
4
+ Addresses the use of `Thread.current` and the potential issues when used in the context of multi-threaded web server and replaces it with `RequestStore` when the gem can be loaded.
5
+
6
+ [request_store](https://github.com/steveklabnik/request_store) is an optional dependency for when working within the context of a multi-threaded web server.
7
+ In that context Threads can be reused for different request causing state from a previous request to stick around to the next request.
8
+ Unless your are manually reinitializing or clearing the state in your own Rack Middleware (at the start of a request) it is recommended that you also include the request_store gem.
9
+
6
10
 
7
11
  > if you use Thread.current, and you use [a multi-threaded web server] ..., watch out! Values can stick around longer than you'd expect, and this can cause bugs."
8
12
 
data/README.md CHANGED
@@ -11,6 +11,8 @@ gem "thread-inheritable_attributes"
11
11
  ```
12
12
 
13
13
  [request_store](https://github.com/steveklabnik/request_store) is an optional dependency for when working within the context of a multi-threaded web server.
14
+ In that context Threads can be reused for different request causing state from a previous request to stick around to the next request.
15
+ Unless your are manually reinitializing or clearing the state in your own Rack Middleware (at the start of a request) it is recommended that you also include the request_store gem.
14
16
 
15
17
  If using Rails no config is required, except including the gem. When using other Rack based frameworks see [docs](https://github.com/steveklabnik/request_store#no-rails-no-problem) for including middleware.
16
18
 
@@ -1,5 +1,5 @@
1
1
  class Thread
2
2
  module InheritableAttributes
3
- VERSION = "1.1.0.beta1"
3
+ VERSION = "1.1.0"
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: thread-inheritable_attributes
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.1.0.beta1
4
+ version: 1.1.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Dustin Zeisler
@@ -91,9 +91,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
91
91
  version: '0'
92
92
  required_rubygems_version: !ruby/object:Gem::Requirement
93
93
  requirements:
94
- - - ">"
94
+ - - ">="
95
95
  - !ruby/object:Gem::Version
96
- version: 1.3.1
96
+ version: '0'
97
97
  requirements: []
98
98
  rubyforge_project:
99
99
  rubygems_version: 2.2.5