On 24 October 2016 at 12:12, Holger Weiß <[email protected]> wrote: > 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)?
Interesting proposal. I don't feel strongly either way (and therefore would lean towards not including it by default, to, you know, keep things simple). However I'd be keen to hear others' thoughts. My feeling is that the potential noise reduction a server could perform from active -> inactive is significant, but inactive -> muted would not be such a significant difference. Important stanzas are typically infrequent, and (assuming the example of a mobile phone) the user may manually check the screen for notifications even if other forms of alerting the user are muted. Second thought: at this point you'd be connected, but implying to the server that you basically don't want to receive any stanzas. Why remain connected? Regards, Matthew _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
