Am 25.01.2013 um 15:12 schrieb Winfried Tilanus <[email protected]>:
> Hi, > > Reading XEP-0198, I was wondering two things: > - Is there a reason acking and resuming, imho two different and > independent things, are in one XEP? In order to resend unacknowledged stanzas upon resuming a stream you need to know about request and anwers. > - Is there also a XEP that takes care of resending a stanza when it does > not get acked? From http://xmpp.org/extensions/xep-0198.html#resumption: When a session is resumed, the parties proceed as follows: • The sequence values are carried over from the previous session and are not reset for the new stream. • Upon receiving a <resume/> or <resumed/> element the client and server use the 'h' attribute to retransmit any stanzas lost by the disconnection. In effect, it should handle the element's 'h' attribute as it would handle it on an <a/> element (i.e., marking stanzas in its outgoing queue as handled), except that after processing it MUST re-send to the peer any stanzas that are still marked as unhandled. • Both parties SHOULD retransmit any stanzas that were not handled during the previous session, based on the sequence number reported by the peer. • A reconnecting client SHOULD NOT request the roster, because any roster changes that occurred while the client was disconnected will be sent to the client after the stream management session resumes. • The client SHOULD NOT resend presence stanzas in an attempt to restore its former presence state, since this state will have been retained by the server. • Both parties SHOULD NOT try to re-establish state information (e.g., Service Discovery [14] information). .Steve
