Keep GraphQL subscriptions active only on a single tab in Web #1047
Labels
enhancement
Improvement of existing features or bugfix
k::refactor
Refactor changes of existing code
Milestone
Background
Remote updates are being received via GraphQL subscriptions.
Problem to solve
Each new instance of application opens the same subscriptions over and over again, even if those instances all share the same database, which just spams the backend and it isn't good.
Possible solutions
Since
drift
supports real-time local changes subscription propagating, this renders having to open multiple GraphQL subscriptions useless: one tab may connect to the updates and the other ones can just get those updates viadrift
subscriptions.Roadmap:
chatEvents
subscription (RefactorRxChat.mesages
pagination towatch()
changes fromdrift
#1060)The text was updated successfully, but these errors were encountered: