Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep GraphQL subscriptions active only on a single tab in Web #1047

Open
1 of 2 tasks
SleepySquash opened this issue Jun 24, 2024 · 0 comments
Open
1 of 2 tasks

Keep GraphQL subscriptions active only on a single tab in Web #1047

SleepySquash opened this issue Jun 24, 2024 · 0 comments
Assignees
Labels
enhancement Improvement of existing features or bugfix k::refactor Refactor changes of existing code
Milestone

Comments

@SleepySquash
Copy link
Contributor

SleepySquash commented Jun 24, 2024

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 via drift subscriptions.

Roadmap:

@SleepySquash SleepySquash added enhancement Improvement of existing features or bugfix k::refactor Refactor changes of existing code labels Jun 24, 2024
@SleepySquash SleepySquash added this to the 0.1.0-alpha.14 milestone Jun 24, 2024
@SleepySquash SleepySquash self-assigned this Jun 24, 2024
@SleepySquash SleepySquash modified the milestones: 0.1.0, 0.2.0 Jun 27, 2024
@SleepySquash SleepySquash modified the milestones: 0.1.3, 0.2.0 Jul 3, 2024
SleepySquash added a commit that referenced this issue Jul 5, 2024
…multaneous execution (#1055, #1047)

Additionally:
- fix `ApplicationSettings` being used with default values by awaiting `SettingsRepository.init()`
github-actions bot added a commit that referenced this issue Jul 5, 2024
…multaneous execution (#1055, #1047)

Additionally:
- fix `ApplicationSettings` being used with default values by awaiting `SettingsRepository.init()` dfef75a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement of existing features or bugfix k::refactor Refactor changes of existing code
Projects
Status: In Progress
Development

No branches or pull requests

1 participant