On 28 Oct 2013, at 17:03, Peter Saint-Andre <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/28/13 9:58 AM, Adán Sánchez de Pedro Crespo wrote: >> Hello everyone, >> >>> Other solutions can be envisioned, for instance using >>> presence=away to signal clients restricting them to send >>> important messages only, queuing not as important messages for >>> later when online, etc. >> >> That's exactly what Loqui IM for Firefox OS does. When the app goes >> to background or the phone is locked, the "show" is changed to >> "away" and the server stops sending it presence stanzas. >> >> It's not elegant at all, but fits the purpose of saving battery >> and keeping the app from being killed by the system. >> >> Do you know of any other better way to implement this? Shouldn't >> we have a standard method to tell a server that it should send a >> client important messages only? > > How do we define "important"? There's the challenge. :-) The - in my view - failed IETF wg SIMPLE worked on this for a while. Maybe their work can be some form of input, even though it is focused on SIP. Filtering may be important: http://tools.ietf.org/html/rfc4660 " This document describes the operations a subscriber performs in order to put filtering rules associated with a subscription to event notification information in place. The handling, by the subscriber, of responses to subscriptions carrying filtering rules and the handling of notifications with filtering rules applied to them are also described. Furthermore, the document conveys how the notifier behaves when receiving such filtering rules and how a notification is constructed." There's also some queing/throttling in RFC 6665. Can't find a good event package that defines throttling. The presence event package just says that a PA should not send a NOTIFY more often than every 5th second. Maybe someone else have a better example. Just some tidbits for the discussion. /O
smime.p7s
Description: S/MIME cryptographic signature
