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

Feature request: implement XEP-0410: MUC Self-Ping optimization #2630

Closed
ge0rg opened this issue Oct 9, 2018 · 2 comments
Closed

Feature request: implement XEP-0410: MUC Self-Ping optimization #2630

ge0rg opened this issue Oct 9, 2018 · 2 comments

Comments

@ge0rg
Copy link

ge0rg commented Oct 9, 2018

It would be great to have a server-side implementation of the round-trip optimization outlined in https://xmpp.org/extensions/xep-0410.html#serveroptimization :

The normal routing rules of the self-ping impose two round-trips: first the initial ping from the client to the MUC, then the reflection of the ping and its response (possibly to another client), and finally the response to the initial IQ. If the other client is experiencing network connectivity issues, which is often the case with mobile devices, the ping request might never be responded to.

Therefore, a MUC service supporting this protocol may directly respond to a participant's Ping request to the participant's own nickname, as opposed to routing it to any of the participant's clients.

This should be a rather straight-forward thing to add to the MUC code. Example implementation from prosody is at https://issues.prosody.im/1220#comment-2

@zinid
Copy link
Contributor

zinid commented Oct 28, 2018

Example implementation from prosody

Nice trolling.

@zinid zinid closed this as completed in 624485f Nov 29, 2018
@lock
Copy link

lock bot commented Nov 29, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants