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

Fingerprint updates not available for unavailable contacts at login #15

Closed
daniele-athome opened this issue Feb 18, 2015 · 3 comments
Closed
Assignees
Milestone

Comments

@daniele-athome
Copy link
Member

Since unavailable presence is not broadcasted when requesting the roster, fingerprint updates are not published at login time. Instead of broadcasting unavailable presences, we could add a fingerprint attribute to the <item/> node at node building time (that is, do not store it).


https://projects.tigase.org/issues/2530#note-16

@daniele-athome daniele-athome added this to the 1.0-alpha2 milestone Feb 18, 2015
@daniele-athome daniele-athome self-assigned this Feb 18, 2015
@daniele-athome daniele-athome modified the milestones: 1.0-alpha2, 1.0-alpha3, 1.0-beta1 Mar 22, 2015
@daniele-athome daniele-athome removed their assignment Mar 23, 2015
@strk
Copy link

strk commented Jul 14, 2015

milestone to be updated ?

@daniele-athome
Copy link
Member Author

It's 1.0-beta1, but the server part release workflow is not well defined yet (meaning to exact ETA).

@daniele-athome
Copy link
Member Author

Superseded by #61.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants