diff options
| author | Ryuta Kamizono <kamipo@gmail.com> | 2017-09-18 15:53:06 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-09-18 15:53:06 +0900 |
| commit | 00cc168f75ebd64e7ecf3c2d12a597fb167747d8 (patch) | |
| tree | c6bc364e40a0a8ac9c018661f5d4d9e367519bd3 /actioncable | |
| parent | 1386efa6864efc69ec6f16633eee1c6c55fc4bfa (diff) | |
| parent | c9527652c753dd8fe3ac120a05f5e80d6d691346 (diff) | |
| download | rails-00cc168f75ebd64e7ecf3c2d12a597fb167747d8.tar.gz rails-00cc168f75ebd64e7ecf3c2d12a597fb167747d8.tar.bz2 rails-00cc168f75ebd64e7ecf3c2d12a597fb167747d8.zip | |
Merge pull request #30642 from ydakuka/quotes
Fix quotes [ci skip]
Diffstat (limited to 'actioncable')
| -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 a060e8938e..70b39ead57 100644 --- a/actioncable/README.md +++ b/actioncable/README.md @@ -454,9 +454,9 @@ The Ruby side of things is built on top of [websocket-driver](https://github.com ## Deployment Action Cable is powered by a combination of WebSockets and threads. All of the -connection management is handled internally by utilizing Ruby’s native thread +connection management is handled internally by utilizing Ruby's native thread support, which means you can use all your regular Rails models with no problems -as long as you haven’t committed any thread-safety sins. +as long as you haven't committed any thread-safety sins. The Action Cable server does _not_ need to be a multi-threaded application server. This is because Action Cable uses the [Rack socket hijacking API](http://www.rubydoc.info/github/rack/rack/file/SPEC#Hijacking) |