mirror of https://github.com/rails/rails
commit
00cc168f75
|
@ -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)
|
||||
|
|
|
@ -954,7 +954,7 @@ to work on some subclass, things get interesting.
|
|||
While working with `Polygon` you do not need to be aware of all its descendants,
|
||||
because anything in the table is by definition a polygon, but when working with
|
||||
subclasses Active Record needs to be able to enumerate the types it is looking
|
||||
for. Let’s see an example.
|
||||
for. Let's see an example.
|
||||
|
||||
`Rectangle.all` only loads rectangles by adding a type constraint to the query:
|
||||
|
||||
|
@ -963,7 +963,7 @@ SELECT "polygons".* FROM "polygons"
|
|||
WHERE "polygons"."type" IN ("Rectangle")
|
||||
```
|
||||
|
||||
Let’s introduce now a subclass of `Rectangle`:
|
||||
Let's introduce now a subclass of `Rectangle`:
|
||||
|
||||
```ruby
|
||||
# app/models/square.rb
|
||||
|
@ -978,7 +978,7 @@ SELECT "polygons".* FROM "polygons"
|
|||
WHERE "polygons"."type" IN ("Rectangle", "Square")
|
||||
```
|
||||
|
||||
But there’s a caveat here: How does Active Record know that the class `Square`
|
||||
But there's a caveat here: How does Active Record know that the class `Square`
|
||||
exists at all?
|
||||
|
||||
Even if the file `app/models/square.rb` exists and defines the `Square` class,
|
||||
|
@ -1049,7 +1049,7 @@ end
|
|||
|
||||
The purpose of this setup would be that the application uses the class that
|
||||
corresponds to the environment via `AUTH_SERVICE`. In development mode
|
||||
`MockedAuthService` gets autoloaded when the initializer runs. Let’s suppose
|
||||
`MockedAuthService` gets autoloaded when the initializer runs. Let's suppose
|
||||
we do some requests, change its implementation, and hit the application again.
|
||||
To our surprise the changes are not reflected. Why?
|
||||
|
||||
|
|
|
@ -382,7 +382,7 @@ Rails 5.1 introduced rails-ujs and dropped jQuery as a dependency.
|
|||
As a result the Unobtrusive JavaScript (UJS) driver has been rewritten to operate without jQuery.
|
||||
These introductions cause small changes to `custom events` fired during the request:
|
||||
|
||||
NOTE: Signature of calls to UJS’s event handlers has changed.
|
||||
NOTE: Signature of calls to UJS's event handlers has changed.
|
||||
Unlike the version with jQuery, all custom events return only one parameter: `event`.
|
||||
In this parameter, there is an additional attribute `detail` which contains an array of extra parameters.
|
||||
|
||||
|
|
Loading…
Reference in New Issue