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

Add support for roster versioning #1106

Closed
jcbrand opened this issue May 24, 2018 · 0 comments
Closed

Add support for roster versioning #1106

jcbrand opened this issue May 24, 2018 · 0 comments
Labels
Feature PWA Progressive web app
Milestone
4.0.0

Comments

@jcbrand
Copy link
Member

jcbrand commented May 24, 2018

Now that presence information is split out from the roster contact models, we can store roster contacts more longer term (in sessionStorage and later in IndexedDB #1105).

However, to avoid letting the roster get out of sync and to avoid having to fetch the whole roster on every login (or reconnection), we need support for roster versioning.
@jcbrand jcbrand added Feature PWA Progressive web app labels May 24, 2018
@jcbrand jcbrand added this to the 4.0.0 milestone May 24, 2018
jcbrand added a commit that referenced this issue May 28, 2018
@jcbrand
Update roster push handling code
43d0932 
- Remove misleading comment and fix conditional logic
- Check that there's only one <item> element.

updates #1106
jcbrand added a commit that referenced this issue May 28, 2018
@jcbrand
Store the roster version
e8a26eb 
updates #1106
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature PWA Progressive web app
Projects
None yet
Milestone
4.0.0
Development

No branches or pull requests
1 participant
@jcbrand