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

Avoid duplicate ATTACH sent #1288

Open
sacOO7 opened this issue Jul 1, 2024 · 0 comments
Open

Avoid duplicate ATTACH sent #1288

sacOO7 opened this issue Jul 1, 2024 · 0 comments
Assignees
@sacOO7

Comments

@sacOO7
Copy link
Collaborator

sacOO7 commented Jul 1, 2024 •
edited by sync-by-unito bot
Loading

  • Attach related changes were introduced as a part of protocol 2.
  • As per protocol 2, ATTACH msg should be sent for every channel in attaching, attached and suspended states once connected.
  • There are various mechanisms by which duplicate ATTACH will be sent
  1. ATTACH is added to the connection or global queue before being sent, check description on -> [ECO-4687][Protocol-2] Fix duplicate outgoing ATTACH msg ably-ruby#416
  2. ATTACH is sent periodically when channel is in SUSPENDED state as per https://sdk.ably.com/builds/ably/specification/main/features/#RTL13b. Timers sending ATTACH periodically can cause duplicate ATTACH being sent on CONNECTED

┆Issue is synchronized with this Jira Task by Unito
@sacOO7 sacOO7 self-assigned this Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sacOO7 sacOO7

Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sacOO7