[Standards] XEP-0369 (MIX) and sorting out co-existence of MUC and MIX on a single domain

Dave Cridland dave at cridland.net
Tue Jan 10 14:43:05 UTC 2017


On 10 January 2017 at 14:37, Kevin Smith <kevin.smith at isode.com> wrote:
>
>
> On 10/01/2017 14:27, Dave Cridland wrote:
>>
>> On 10 January 2017 at 13:30, Kevin Smith <kevin.smith at isode.com> wrote:
>>>
>>> On 10/01/2017 12:05, Steve Kille wrote:
>>>>
>>>> I have just issued a PR for MIX version 0.6.4.
>>>>
>>>> There is clear desire to have the option for  MUC and MIX to use the
>>>> same
>>>> domain.    The difficulty in achieving this was incompatible disco
>>>> results.
>>>> This version has made a change to
>>>>     add node='mix' to channel disco that will enable the queries to be
>>>> disambiguated.
>>>
>>> I haven't been able to think of a case other than disco#items on the room
>>> JID where MUC and MIX are likely to collide. This change doesn't make it
>>> *easy* to implement both on the same domain, but I think it makes it
>>> viable
>>> - please shout if anyone can think of other cases.
>>>
>> I agree. Further, I only know of a single client that would ever hit
>> disco#items on a room, and that's Psi in its generic disco "browser".
>>
> Are you suggesting that this approach isn't necessary, and it'd be
> sufficient to 'break' disco#items handling for MUC-only clients?
>

I'd not thought of this approach, but I was considering advocating
"just break". I think this means we don't have to.

>
> /K
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________


More information about the Standards mailing list