https://mail.jabber.org/pipermail/standards/2016-February/030925.html
The follow up message from Holger (Timeout only starts after first push-worthy stanza) is also important. We also came to the conclusion that it is desirable to actively close the TCP connection if an <r/> from the server remains unanswered after ~30 seconds or so. This is due to some platforms (read Android) not allowing us to properly close the connection ourself. (But this is probably a business rule for SM and not for Push). It also handled in that module. Both the prosody module as well as the unpublished ejabberd follow those business rules. cheers Daniel 2017-05-24 21:28 GMT+02:00 Kevin Smith <[email protected]>: > > >> On 24 May 2017, at 20:24, Daniel Gultsch <[email protected]> wrote: >> >> 2017-05-24 21:16 GMT+02:00 Evgeny Khramtsov <[email protected]>: >>> Since we're discussing this: what about XEP-0357 (Push Notifications)? >>> Is it gonna be deferred? What's its state? >> >> The author is unresponsive and has been ignoring my feedback for over a year. >> >> Implementation wise it's looking relativity fine. I'm using this >> successfully on a daily basis. (With my proposed changes) > > Would you mind resharing your proposals please? I'm interested in push right > now. > > /K > >> >> cheers >> Daniel >> _______________________________________________ >> Standards mailing list >> Info: https://mail.jabber.org/mailman/listinfo/standards >> Unsubscribe: [email protected] >> _______________________________________________ > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
