[Standards] XEP-0369 (MIX): When to deliver messages to a client

Kevin Smith kevin.smith at isode.com
Wed Jun 14 08:05:11 UTC 2017


On 14 Jun 2017, at 09:02, Kevin Smith <kevin.smith at isode.com> wrote:
> 
> On 14 Jun 2017, at 08:53, Kevin Smith <kevin.smith at isode.com> wrote:
>> 
>> On 14 Jun 2017, at 08:23, Steve Kille <steve.kille at isode.com> wrote:
>>> 
>>> Jonas,
>>> 
>>>> 
>>>> From <https://github.com/xsf/xeps/compare/
>>>> master...stevekille:MIX#diff-46551996fe454185b68cb3f084c2e18fR2426>:
>>>> 
>>>>> The server receiving the message will then deliver the messages to all
>>>>> online clients with status available and a non-negative resource priority.
>>>> 
>>>> I think the new wording here excludes any client with e.g. away, na, dnd or
>>>> xa status from receiving MIX messages. That sounds like overkill (I’m not
>>>> even sold on not receiving MIX messages with negative presence priority
>>>> actually).
>>> [Steve Kille] 
>>> 
>>> You asked me to fix an ambiguity, which I did!
>> 
>> I think you simply mean ‘an available resource’ rather than ’status available’, which are very different.
>> 
>>> I guess that we now need to work out the situations when to not deliver MIX messages to  a client.
>> 
>> When it’s an available resource and it supports MIX, presumably?
> 
> In retrospect, I think an interested resource is probably a better call than an available resource, given the roster interactions.

(Interested *and* available)


More information about the Standards mailing list