[Standards] XEP-0198: Stream should be closed when 'h' value is to high

Jonas Wielicki jonas at wielicki.name
Wed Feb 21 09:41:36 UTC 2018

On Mittwoch, 21. Februar 2018 10:32:37 CET Kevin Smith wrote:
> At first glance, its seems to me like this can only happen when an entity’s
> 198 support is broken in some way. If that’s the case, would we expect the
> same entity to reconnect and do the same thing again? If so, is it better
> to continually disconnect due to bad-h, reconnect, etc., or to do the best
> we can to keep the stream up?

The entity shouldn’t be reconnecting after a stream error, so the loop you’re 
talking about won’t happen (unless the entity is also broken in other ways, 
but one can construct arbitrary failure modes if we assume that).

> It’s not clear to me that closing the stream improves matters here if such a
> thing reaches the wild, although the suggestion made later that it helps
> cause failures during dev is probably reasonable.


kind regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.jabber.org/pipermail/standards/attachments/20180221/fff969fb/attachment.sig>

More information about the Standards mailing list