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

Publisher Worker Queue: Update Resolution #566

Open
AndyTWF opened this issue Feb 16, 2023 · 1 comment
Open

Publisher Worker Queue: Update Resolution #566

AndyTWF opened this issue Feb 16, 2023 · 1 comment
Milestone

Comments

@AndyTWF
Copy link
Contributor

AndyTWF commented Feb 16, 2023

Implement the following AAT Android worker:

  • UpdateResolution
  • UpdateResolutionSuccess

UpdateResolution is responsible for updating the Publishers presence data when a new resolution is resolved (in publisher.resolveResolution).

If the resolution is not currently queued for update, it is added to a list of publisher resolutions to be updated. If the resolution is not the latest resolution to be added (for example, in practice, another has come along and the presence update failed), then it is removed and the operation terminates.

Otherwise, we wait for the ably channel to attach and update presence data to include the latest resolution. If this results in a fatal error or is successful, UpdateResolutionSuccess work is posted. Otherwise, the resolution update is retried.

The UpdateResolutionSuccess worker removes the resolution from the update queue.

This work depends on:

This work is implemented almost identically to the workers in the following task, so may benefit from taking what's already been done:

@AndyTWF AndyTWF added this to the 1.0.0 milestone Feb 16, 2023
@sync-by-unito
Copy link

sync-by-unito bot commented Feb 16, 2023

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3379

@AndyTWF AndyTWF changed the title Worker Queue: Update Resolution Publisher Worker Queue: Update Resolution Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant