FYI.

-------- Original Message --------
Subject: Re: [MUC] XEP-0249 and "continue"
Date: Tue, 16 Aug 2011 15:27:21 -0600
From: Peter Saint-Andre <[email protected]>
Reply-To: Multi-User Chat over XMPP <[email protected]>
To: [email protected], Multi-User Chat over XMPP <[email protected]>

On 8/16/11 1:40 PM, Kevin Smith wrote:
> On Tue, Aug 16, 2011 at 8:34 PM, Peter Saint-Andre <[email protected]> wrote:
>> I'm working my way through a backlog of open issues related to MUC, so
>> you might see a few messages on the list here soon.
>>
>> Someone pointed out to me that the direct invitation method (XEP-0249)
>> does not have feature-parity with the mediated invitation method because
>> in XEP-0045 the inviter can indicate that the room is a continuation of
>> an existing one-to-one thread:
>>
>> <message
>>    from='[email protected]/desktop'
>>    id='gl3s85n7'
>>    to='[email protected]'>
>>  <x xmlns='http://jabber.org/protocol/muc#user'>
>>    <invite to='[email protected]'>
>>      <reason>
>>        Hey Hecate, this is the place for all good witches!
>>      </reason>
>>      <continue thread='e0ffe42b28561960c6b12b944a092794b9683a38'/>
>>    </invite>
>>  </x>
>> </message>
>>
>> Contrast with XEP-0249:
>>
>> <message
>>    from='[email protected]/desktop'
>>    to='[email protected]'>
>>  <x xmlns='jabber:x:conference'
>>     jid='[email protected]'
>>     password='cauldronburn'
>>     reason='Hey Hecate, this is the place for all good witches!'/>
>> </message>
>>
>> In version 1.1 of XEP-0249 we added the optional 'reason' attribute. I
>> think we could similarly add an optional 'continue' attribute (with a
>> datatype of boolean):
>>
>> <message
>>    from='[email protected]/desktop'
>>    to='[email protected]'>
>>  <x xmlns='jabber:x:conference'
>>     continue='true'
>>     jid='[email protected]'
>>     password='cauldronburn'
>>     reason='Hey Hecate, this is the place for all good witches!'/>
>> </message>
>>
>> We could also add an optional thread attribute:
>>
>> <message
>>    from='[email protected]/desktop'
>>    to='[email protected]'>
>>  <x xmlns='jabber:x:conference'
>>     continue='true'
>>     jid='[email protected]'
>>     password='cauldronburn'
>>     reason='Hey Hecate, this is the place for all good witches!'
>>     thread='e0ffe42b28561960c6b12b944a092794b9683a38'/>
>> </message>
>>
>> Yes, it's unfortunate to be adding attributes to "jabber:x:conference"
>> at this point, but the new attributes are backward-compatible.
> 
> This seems reasonable.

http://xmpp.org/extensions/tmp/xep-0249-1.2.html

http://xmpp.org/extensions/diff/api/xep/0249/diff/1.1/vs/1.2rc1

/psa

Reply via email to