mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
ca06a9ff41
We refer to `model` elsewhere in Action Cable's implementation, so use the same in `stream_or_reject_for` as well to keep the consistency. Simplify the docs for the method to remove the usage "intention" (that's not up to us) and mention it rejects the "subscription", not the "connection". |
||
|---|---|---|
| .. | ||
| 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: