[Bug 39630] New: MUC: don't rely on message id=''s for delivery reports

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=39630

           Summary: MUC: don't rely on message id=''s for delivery reports
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: gabble
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: will.thompson at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


M-Link, as used by jabber.org, does not include the id='' you set on messages
sent to a MUC on the echoes it sends back.

David Cridland sez: “The ids last, in my opinion, as long as the rest of the
"header" - the from/to etc. [...] M-Link will in some cases [modify the message
body,] which is another argument against repeating the id blindly.”

A bunch of people disagree with him; I'm not sure whether I agree or not. But
we could potentially deal with this by having Gabble keep a list of pending
messages and matching up messages from ourself against them. (This does not
work if you're joined to the same MUC twice using the same MUC JID, which I
believe is possible …)

M-Link leaves the id='' intact if it's sending back a <message type='error'/>,
so we can continue to rely on this for failure reports in any case.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.