diff options
author | Yves Senn <yves.senn@gmail.com> | 2015-12-19 14:42:09 +0100 |
---|---|---|
committer | Yves Senn <yves.senn@gmail.com> | 2015-12-19 14:42:09 +0100 |
commit | 8615f8b5c8bee0d32518bdc33f02faf68284ed94 (patch) | |
tree | 3e18ca45e424ff329446f88eccb873bf5b6d2995 | |
parent | f95557b47f8fe21dd7b16b30b89ff098e2916f89 (diff) | |
download | rails-8615f8b5c8bee0d32518bdc33f02faf68284ed94.tar.gz rails-8615f8b5c8bee0d32518bdc33f02faf68284ed94.tar.bz2 rails-8615f8b5c8bee0d32518bdc33f02faf68284ed94.zip |
docs, follow up to #22699. [ci skip]
-rw-r--r-- | actioncable/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/actioncable/README.md b/actioncable/README.md index d3902f53d1..32f49c215f 100644 --- a/actioncable/README.md +++ b/actioncable/README.md @@ -16,7 +16,7 @@ WebSockets open to your application if they use multiple browser tabs or devices The client of a WebSocket connection is called the consumer. Each consumer can in turn subscribe to multiple cable channels. Each channel encapsulates -a logical unit of work, similar to what a controller does in a regular MVC setup. For example, +a logical unit of work, similar to what a controller does in a regular MVC setup. For example, you could have a `ChatChannel` and a `AppearancesChannel`, and a consumer could be subscribed to either or to both of these channels. At the very least, a consumer should be subscribed to one channel. @@ -395,7 +395,7 @@ bundle exec puma -p 28080 cable/config.ru ``` The above will start a cable server on port 28080. Remember to point your client-side setup against that using something like: -`App.cable = Cable.createConsumer("ws://basecamp.dev:28080")`. +`App.cable = ActionCable.createConsumer("ws://basecamp.dev:28080")`. ### In app |