| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
Support faye-websocket + EventMachine as an option
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Fixes #22675
Allow channel identifiers and also data with no backslahes/escaping to be accepted by
the subscription storer.
|
|\ \
| | |
| | |
| | | |
ActionCable: Add a "welcome" and "ping" message type
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change makes ping into a message type, which
makes the whole protocol a lot more consistent.
Also fixes hacks on the client side to make this all
work.
|
| | | |
|
|\ \ \
| |_|/
|/| | |
convert cable.coffee to cable.js
|
| | |
| | |
| | |
| | | |
In order to eliminate the dependecy of CoffeeScript.
|
| |/
|/| |
|
|\ \
| |/
|/| |
Ensure actioncable behaves as expected with non-string queues
|
| |
| |
| |
| |
| |
| | |
Similar to the channel streaming side, these values must be strings for
ActionCable to behave as expected. The conversion will allow users to
send string-convertible values and get the expected behavior.
|
| |
| |
| |
| |
| |
| |
| | |
ActionCable does some things behind the scenes that expects these
"broadcasting"s or "channel"s to be strings. However it's not
immediately obvious that the value must be a string. So adding this
conversion ensures things work as expected.
|
| |
| |
| |
| |
| | |
* Fix typos/grammar errors
* Make capitalization/naming consistent
|
|\ \
| | |
| | |
| | |
| | | |
lifo/same-redis-connection-for-subscription-and-broadcast
Always use redis_connector to create redis connections
|
| | |
| | |
| | |
| | | |
broadcasts
|
| | |
| | |
| | |
| | | |
If we're deferring one, we should defer the other too.
|
|\ \ \
| | | |
| | | | |
Only hijack Rack socket when first needed
|
| | |/
| |/|
| | |
| | | |
Fixes #23471
|
|/ /
| |
| |
| | |
This also marks Action Cable routes as internal to Rails.
|
| | |
|
|\ \
| | |
| | | |
Improve Action Cable reconnection reliability
|
| |/ |
|
|\ \
| | |
| | | |
Full Action Cable documentation read through
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This PR checks all active Action Cable documentation for typos and other
fixes. It aims to make sure that when Rails 5 is released, that the
Action Cable docs are up to snuff with the other documentation included
with Rails.
[ci skip]
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Once RubyGems 2.5.0 is required, then the duplicated files can be
removed, and symlinks can be used instead.
[ci skip]
|
| |/
|/| |
|
| | |
|
|\ \
| | |
| | | |
Make ActionCable logging less verbose in development
|
| |/
| |
| |
| |
| |
| | |
When running the ActionCable server in development I get a lot of output
in my logs, this commit sets a maximum length of 300 characters for a
broadcast log message.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Before this commit, the `unsubscribed` callbacks in Action Cable server
side channels were never called. This is because when a WebSocket
"goodbye" message was sent from the client, the Action Cable server
didn't properly clean up after the now closed WebSocket. This means that
memory could possibly skyrocket with this behavior, since part of this
commit is to properly remove closed subscriptions from the global
subscriptions hash. Say you have 10,000 users currently connected, and
then all 10,000 disconnect -- before this patch, Action Cable would
still hold onto information (and Ruby objects!) for all of these now
dead connections.
|
|\
| |
| | |
Inject Rails related configuration through Railtie
|
| |
| |
| |
| |
| |
| |
| | |
Instead of depending on ApplicationCable::Connection being defined at initialize
we should inject it in the Railtie.
Thus we can kill more setup in the tests too.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We were explicitly referencing Rails.root in ActionCable::Server::Configuration.initialize,
thereby coupling ourselves to Rails.
Instead add `app/channels` to Rails' app paths and assign the existent files
to `channel_paths`.
Users can still append to those load paths with `<<` and `push` in `config/application.rb`.
This means we can remove the custom `Dir` lookup in `channel_paths` and the Rails
and root definitions in the tests.
|
| | |
|
|\| |
|
| |
| |
| |
| | |
Follow up to 6accef4e11b0c793e1c085536b5ed27f32b6a0c3
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Properly indent code sample in ActionCable::Channel::Streams
* Add a doc comment for #stop_all_streams
* Reformat + add <tt> blocks around code references in ActionCable::Base docs
* Clarify and a little better grammar on ActionCable::RemoteConnections
* Correct indentation and clean up ActionCable::Server::Broadcasting code sample
|
| | |
|
| |\
| | |
| | | |
Redis sans EventMachine
|
| | |
| | |
| | |
| | |
| | |
| | | |
This new adapter does get a little more intimate with the redis-rb gem's
implementation than I would like, but it's the least bad of the
approaches I've come up with.
|
| | | |
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
Also, address the possibility of the listen thread dying and needing to
be respawned. As a bonus, we now defer construction of the thread until
we are first given something to monitor.
|
| |
| |
| |
| | |
They're all at risk of races on the first requests.
|
| | |
|
| | |
|
| | |
|
| | |
|