mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
267e1d25dc
To assist in various debugging scenarios, such as [tracking which types of threads are using db connections][0] Thread names will now be "ActionCable-worker-N" instead of "worker-N". This is safe for all ruby versions. In versions which do not have thread names, [concurrent-ruby does not attempt to add the name][1] In the environment I happened to be testing in: ```ruby e = Concurrent::ThreadPoolExecutor.new(name: 'ActionCable', min_threads: 2, max_threads: 2) e.post{sleep 100} e.post{sleep 100} Thread.list.map(&:name) ``` [0] https://github.com/puma/puma/issues/1512#issuecomment-756760388 [1] https://github.com/ruby-concurrency/concurrent-ruby/blob/master/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb#L312 |
||
---|---|---|
.. | ||
app | ||
bin | ||
lib | ||
test | ||
.babelrc | ||
.eslintrc | ||
.gitignore | ||
actioncable.gemspec | ||
CHANGELOG.md | ||
karma.conf.js | ||
MIT-LICENSE | ||
package.json | ||
Rakefile | ||
README.md | ||
rollup.config.js | ||
rollup.config.test.js |
Action Cable – Integrated WebSockets for Rails
Action Cable seamlessly integrates WebSockets with the rest of your Rails application. It allows for real-time features to be written in Ruby in the same style and form as the rest of your Rails application, while still being performant and scalable. It's a full-stack offering that provides both a client-side JavaScript framework and a server-side Ruby framework. You have access to your full domain model written with Active Record or your ORM of choice.
You can read more about Action Cable in the Action Cable Overview guide.
Support
API documentation is at:
Bug reports for the Ruby on Rails project can be filed here:
Feature requests should be discussed on the rails-core mailing list here: