On 24.10.2016 13:12, Holger Weiß wrote: > As per XEP-0352, a client is currently either <active/> or <inactive/>. > The inactive state permits the server to perform optimizations based on > the assumption that the user is currently not interacting with the > client. However, as the client might still generate notifications to > attract the user's attention, the suggestion is that only "unimportant" > stanzas should be affected by those optimizations. > > Wouldn't it make sense to have another client state (<muted/> or > whatever) for the case where the client won't generate notifications, so > the server could perform additional optimizations (such as also queueing > <message/> stanzas)?
I don't see how a mobile client would benefit from such a state. If we have a state where the server would queue <message/> stanzas, then the client could go offline as well. - Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
