* Philipp Hancke <fi...@goodadvice.pages.de> [2019-09-03 14:15]: > 0353 was explicitly designed for push (by not including the full payload due > to size constraints) in conjunction with 0357 and should not go to MAM > (hence no body).
Let's imagine the following: - 0353 or 0313 get changed to store all 0353 messages into MAM - a remote entity sends a <propose/> - the user's server stores the <propose/> into MAM - 0357 triggers a push on this new MAM message - the (mobile) client connects and fetches MAM - the client sees a <propose/> that was neither retracted, rejected or accepted and is sufficiently recent (say, last 30 second) - the client <accept/>s the call @Andrew, would this be sufficient to make the protocol work for your iOS case? A side benefit of this would be that both the call itself and whether it was accepted/rejected is stored in MAM and can be displayed in the client's message history. Speaking of 0353 as is, it was also not designed for Carbons. I think we should explicitly make use of Carbons (by similar means as with MAM), so that we do not need separate <accept/> (to self) and <proceed/> (to the initator) messages. Instead, the <proceed/> will be carbon-copied to all other resources, letting them know that one client accepted the call. Georg -- || http://op-co.de ++ GCS d--(++) s: a C+++ UL+++ !P L+++ !E W+++ N ++ || gpg: 0x962FD2DE || o? K- w---() O M V? PS+ PE-- Y++ PGP+ t+ 5 R+ || || Ge0rG: euIRCnet || X(+++) tv+ b+(++) DI+++ D- G e++++ h- r++ y? || ++ IRCnet OFTC OPN ||_________________________________________________||
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
