Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Don't inherit from Concurrent::CountDownLatch | Matthew Draper | 2016-03-11 | 1 | -5/+12 |
| | | | | | | | | | | | That class mangles .new, which interferes with our deprecation warning. More generally, it suggests we shouldn't be subclassing without a very good reason, and avoiding one allocation doesn't seem to meet that criteria. In passing, recommend the simpler Concurrent::Event for the common count=1 case. | ||||
* | Require only necessary concurrent-ruby classes. | Jerry D'Antonio | 2015-11-04 | 1 | -2/+2 |
| | |||||
* | Replaced `ActiveSupport::Concurrency::Latch` with concurrent-ruby. | Jerry D'Antonio | 2015-07-13 | 1 | -16/+8 |
| | | | | | | | | | | The concurrent-ruby gem is a toolset containing many concurrency utilities. Many of these utilities include runtime-specific optimizations when possible. Rather than clutter the Rails codebase with concurrency utilities separate from the core task, such tools can be superseded by similar tools in the more specialized gem. This commit replaces `ActiveSupport::Concurrency::Latch` with `Concurrent::CountDownLatch`, which is functionally equivalent. | ||||
* | added live responses which can be written and read in separate threads | Aaron Patterson | 2012-07-29 | 1 | -0/+27 |