virtuacoplenny 84b589719f fix(connection): reload immediately on possible split-brain (#3162) ... * fix(connection): reload immediately on possible split-brain There isn't an explicit way to know when a split brain scenario has happened. It is assumed it arises when an "item-not-found" connection error is encountered early on in the conference. So, store when a connection has happened so it be calculated how much time has elapsed and if the threshold has not been exceeded then do an immediate reload of the app instead of showing the overlay with a reload timer. * squash: rename isItemNotFoundError -> isShardChangedError		2018-07-02 16:22:51 -05:00
..
actionTypes.js	Refactor settings modal (#3121)	2018-06-20 13:19:53 -07:00
actions.js	[RN] Handle presence	2018-06-22 12:22:12 +02:00
constants.js	feat(1080p): pass new-style constraints to createLocalTracks (#2087)	2017-10-31 17:08:07 -07:00
functions.js	Token based features (#3075)	2018-06-15 13:10:22 -05:00
index.js	[RN] fix(Avatar): Match the implementation for web	2017-03-08 13:21:34 -06:00
middleware.js	fix(connection): reload immediately on possible split-brain (#3162)	2018-07-02 16:22:51 -05:00
reducer.js	Refactor settings modal (#3121)	2018-06-20 13:19:53 -07:00