84b589719f
* 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 |
||
|---|---|---|
| .. | ||
| actionTypes.js | ||
| actions.native.js | ||
| actions.web.js | ||
| functions.js | ||
| index.js | ||
| reducer.js | ||