[Standards] s2s and gracelessly broken streams
Justin Karneges
justin-keyword-jabber.093179 at affinix.com
Wed Apr 4 18:03:42 CDT 2007
On Wednesday 04 April 2007 2:32 pm, Matthias Wimmer wrote:
> Justin Karneges schrieb:
> > XEP-198 effectively handles this. If the client doesn't wait too long to
> > reconnect, then the session can be resumed (if the server supports it).
>
> Does it? I can't find a way to resume a session with this XEP.
Example 9, 10.
The 'b' attribute indicates the last stanza received. Both parties can send
this attribute, although in the example the client does not send it for some
reason. This is enough information to know what was not received by the
other party, and the stanzas can be re-sent.
It is not mentioned in the XEP, but the client should probably be required to
bind to the same resource again, when using resume.
-Justin
More information about the Standards
mailing list