#1220 muc: implement XEP-0410: MUC Self-Ping optimization

Reporter ge0rg
Owner Zash
Stars ★ (1)
  • Priority-Medium
  • Type-Enhancement
  • Milestone-0.11
  • Status-Fixed
  1. ge0rg on

    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 (and a backport to 0.10 will be greatly anticipated).

  2. Zash on

    Added in trunk: https://hg.prosody.im/trunk/rev/7c1cdf5f9f83 Also https://modules.prosody.im/mod_muc_ping.html for 0.10 and older.

    • tags Milestone-0.11 Status-Fixed
    • owner Zash
  3. ge0rg on

    Thanks very much for the implementation! Do I have to load mod_muc_ping on the MUC component?

  4. Zash on

    Yes, goes on the component.

New comment

Not published. Used for spam prevention and optional update notifications.