moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 15:18:51 -05:00
Code Issues Releases Wiki Activity

XEP-0124: Fix typo and DTD

Browse Source
This commit is contained in:
Sam Whited 2016-11-14 16:37:29 -06:00
parent dc4c0b1dc5
commit e14fc079f2
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
xep-0124.xml
View File

@ -12,7 +12,8 @@
<number>0124</number>
<status>Draft</status>
<type>Standards Track</type>
<jig>Standards</jig>
<sig>Standards</sig>
<approver>Council</approver>
<dependencies>
<spec>RFC 1945</spec>
<spec>RFC 2616</spec>
@ -30,6 +31,12 @@
&metajack;
&lance;
&winfried;
<revision>
<version>1.11.1</version>
<date>2016-11-16</date>
<initials>XEP Editor: ssw</initials>
<remark><p>Minor typo and DTD fixes.</p></remark>
</revision>
<revision>
<version>1.11</version>
<date>2014-04-09</date>
@ -498,7 +505,7 @@ Content-Length: 69
<body ack='1249243564'
xmlns='http://jabber.org/protocol/httpbind'/>]]></example>
<p>If the connection manager will be including 'ack' attributes on responses during a session, then it MUST include an 'ack' attribute in its session creation response, and set the 'ack' attribute of responses throughout the session. The only exception is that, after its session creation response, the connection manager SHOULD NOT include an 'ack' attribute in any response if the value would be the 'rid' of the request being responded to.</p>
<p>If the connection manager is permitted to hold more than one request at a time, then the reception of a lower-than-expected 'ack' value from the connection manager (or the unexpected abscence of an 'ack' attribute) can give the client an early warning that a network failure might have occurred (e.g., if the client believes the connection manager should have received another request by the time it responded).</p>
<p>If the connection manager is permitted to hold more than one request at a time, then the reception of a lower-than-expected 'ack' value from the connection manager (or the unexpected absence of an 'ack' attribute) can give the client an early warning that a network failure might have occurred (e.g., if the client believes the connection manager should have received another request by the time it responded).</p>
</section2>
<section2 topic='Response Acknowledgements' anchor='ack-response'>
<p>The client MAY similarly inform the connection manager about the responses it has received by setting the 'ack' attribute of any request to the value of the highest 'rid' of a request for which it has already received a response in the case where it has also received all responses associated with lower 'rid' values. If the client will be including 'ack' attributes on requests during a session, then it MUST include an 'ack' attribute (set to '1') in its session creation request, and set the 'ack' attribute of requests throughout the session. The only exception is that, after its session creation request, the client SHOULD NOT include an 'ack' attribute in any request if it has received responses to all its previous requests.</p>