rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Defer starting connection monitor until a connection is opened	Javan Makhmali	2016-03-03	1	-3/+7
\|
*	Establish WebSocket connection when first subscription is created. Fixes #24026	Javan Makhmali	2016-03-03	1	-8/+5
\| \| \| \| \|	* More intention revealing than connecting on the first call to Connection#send * Fixes that calls to Connection#send would attempt to open a connection when the WebSocket's state is CONNECTING
*	ConnectionMonitor is once again notified of disconnect	Daniel Rhodes	2016-03-03	1	-0/+1
\|
*	Make ping into a message type	Daniel Rhodes	2016-03-01	1	-2/+3
\| \| \| \| \| \| \| \|	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.
*	Added welcome message type and fix test hacks	Daniel Rhodes	2016-03-01	1	-0/+2
\|
*	Only open Action Cable connection if data is being sent	Jon Moss	2016-02-24	1	-1/+3
\|
*	Fix isAlive condition and add more logging	Javan Makhmali	2016-02-23	1	-5/+7
\|
*	ActionCable.log	Javan Makhmali	2016-02-23	1	-7/+7
\|
*	Uninstall event handlers when replacing WebSocket instance	Javan Makhmali	2016-02-23	1	-0/+6
\| \| \| \|	Ensures we don't get "onclose" events from a previous WebSocket that was in the "closing" state
*	Connection#isAlive	Javan Makhmali	2016-02-23	1	-3/+3
\|
*	Treat 'closing' state as closed.	Pratik Naik	2016-02-23	1	-3/+6
\| \| \| \| \| \|	We are seeing cases where the websockets get stuck in the 'closing' state after a tab has been in background for a while. So lets treat those websockets as closed.
*	Add client-side console logging to help debug reconnect issues	Javan Makhmali	2016-02-23	1	-0/+7
\|
*	Wrangle the asset build into something that sounds more general	Matthew Draper	2016-02-01	1	-0/+81