From bd2b1ac70062dcf29db03dcdbfc9ea7029212a85 Mon Sep 17 00:00:00 2001 From: Tobias Markmann Date: Wed, 7 Jul 2010 16:50:40 +0000 Subject: [PATCH] Fixing example. git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@4293 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0198.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0198.xml b/xep-0198.xml index 11369f21..1e4e4272 100644 --- a/xep-0198.xml +++ b/xep-0198.xml @@ -231,9 +231,9 @@ C: -C: +C: -S: +S: ]]>

When an <r/> element ("request") is received, the recipient MUST acknowledge it by sending an <a/> element to the sender containing a value of 'h' that is equal to the number of stanzas handled by the recipient of the <r/> element. The response SHOULD be sent as soon as possible after receiving the <r/> element, and MUST NOT be withheld for any condition other than a timeout. For example, a client with a slow connection might want to collect many stanzas over a period of time before acking, and a server might want to throttle incoming stanzas. The sender does not have to wait for an ack to continue sending stanzas. Because acks indicate stanza acceptance, a server that is throttling stanzas MUST delay the response until the client is no longer being penalized (but SHOULD notify the client that it is throttling incoming stanzas, as described under Throttling).

When a party returns an ack in response to an <r/> element or receives such an ack, it SHOULD keep a record of the 'h' value returned as the sequence number of the last handled stanza for the current stream (and discard the previous 'h' value).