Quantcast
Channel: Ignite Realtime : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 10742

MUC Mediated vs Direct Invite bug?

$
0
0

This is regarding Example/Listing 57 of the MUC XEP (XEP-0045).

 

When a server forwards a mediated invite to a destination JID, the invite according to the XEP looks like this;

 

<message
    from='coven@chat.shakespeare.lit'
    id='nzd143v8'
    to='hecate@shakespeare.lit'>
  <xxmlns='http://jabber.org/protocol/muc#user'>
    <invitefrom='crone1@shakespeare.lit/desktop'>
      <reason>
        Hey Hecate, this is the place for all good witches!
      </reason>
    </invite>
    <password>cauldronburn</password>
  </x>
</message>

 

But Openfire (3.8.2) send the following;

 

<message
from='coven@chat.shakespeare.lit'
id='nzd143v8'
to='hecate@shakespeare.lit'>
<xxmlns='http://jabber.org/protocol/muc#user'>
<invitefrom='crone1@shakespeare.lit/desktop'>
<reason>
        Hey Hecate, this is the place for all good witches!
</reason>
</invite>
<password>cauldronburn</password>
</x>   <x xmlns="jabber:x:conference" jid="coven@chat.shakespeare.lit'"/>
</message>

 

The text highlighted in red appears to be surplus to requirement. I thought the presence of  ‘jabber:x:conference’ was meant for Direct invites (XEP 0249) as opposed to those that are mediated. I was wondering if there was a particular reason for this extra line.

 

 

Many thanks for you time.

  1. Don.

Viewing all articles
Browse latest Browse all 10742

Trending Articles