-
-
Notifications
You must be signed in to change notification settings - Fork 328
Closed as not planned
Labels
priority-2-moderateShould be resolved on a reasonable timeline.Should be resolved on a reasonable timeline.release-patchWarrents a patch releaseWarrents a patch releasetype-javascriptRelated to client-side codeRelated to client-side code
Description
Current Situation
Currently we implement our own reconnecting webscoket which is deficient in one way I do know, and probably others I'm unaware of. The one I know, is that we don't stop trying to reconnect after the connection is closed due to an error. Keeping track of how to respond in the case of each error code isn't something we should have to deal with. We should just use a library.
Proposed Actions
Archmonger
Metadata
Metadata
Assignees
Labels
priority-2-moderateShould be resolved on a reasonable timeline.Should be resolved on a reasonable timeline.release-patchWarrents a patch releaseWarrents a patch releasetype-javascriptRelated to client-side codeRelated to client-side code