* Andrew Nenakhov <[email protected]> [2020-09-29 02:22]: > From our experience, the absence of mandatory stable message IDs is the > biggest design flaw of XMPP as a protocol (resource priorities take the > second place), and fixing this was the first thing we did when we > started implementing our improvements to the protocol.
Basically, I agree. It's just that I see more value in interop than you seem to do, so I'm more interested in fixing our specs than in implementing custom solutions. Which is obviously harder. FWIW, if I were to start from scratch, I'd probaby push this down to the stream management layer. The server could acknowledge each and every stanza with something like: | <a client_id='1234' server_id='5678' archived='urn:xmpp:mam:2'/> Would get us rid of 0198's stanza counting, and of the <r/>equest traffic. However, if the server also needs ACKs from the client (to offer stream resumption), this starts becoming messy, as the server can't tag IQs with stanza IDs. Holger _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
