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.

Sign up for GitHub

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

Jump to bottom

[Access] Unify subscription and client IDs #6845

Open
Tracked by #6163
illia-malachyn opened this issue Jan 3, 2025 · 0 comments · May be fixed by #6847
Open
Tracked by #6163

[Access] Unify subscription and client IDs #6845

illia-malachyn opened this issue Jan 3, 2025 · 0 comments · May be fixed by #6847
Assignees
@illia-malachyn

Comments

@illia-malachyn
Copy link
Contributor

illia-malachyn commented Jan 3, 2025 •
edited
Loading

After a short investigation, it turned out that we don't need to have 2 IDs per subscription. We can use 1 to cover all requirements/features we need.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@illia-malachyn illia-malachyn

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Access] Unify subscription id with client message id The-K-R-O-K/flow-go
1 participant
@illia-malachyn