I totally agree with that. Thanks for your response. I'm wondering if this should somehow be reflected in the XEP.
Best regards Michal Piotrowski michal.piotrow...@erlang-solutions.com On 14 February 2017 at 14:20, Georg Lukas <ge...@op-co.de> wrote: > * Michal Piotrowski <michal.piotrow...@erlang-solutions.com> [2017-02-14 > 12:18]: > > I'm currently investigating following situation. The server sent to the > > client 10 stanzas and clients sends accept <a h='11'/> which is not valid > > (too high). > > In XEP-0198 I didn't find any information what should happen if clients > > sends too high 'h' parameter. > > I would suggest terminating the session with a policy-violation both for > the <a> and <resume> cases. An invalid 'h' value is an indication of a > client implementation bug, and those are really hard to debug. Killing > the session on sight will make the client developer more aware of the > issue, preventing looming desynchronization problems like a mismatch in > the number of actually processed and user-displayed messages. > > > 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 ||_________________________________________________|| > > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ > >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
