Removing duplicate "hold" attribute in session creation response (paragraph
7.2), "hold" keeping it as a SHOULD. Moving "requests" to the attributes
that MUST be present. See also:
http://wiki.xmpp.org/web/BoshIssues#Session_Creation_Attributes_Too_Optional
Signed-off-by: Winfried Tilanus <winfr...@tilanus.com>
---
extensions/xep-0124.xml | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/extensions/xep-0124.xml b/extensions/xep-0124.xml
index c0c45d4..214c61c 100644
--- a/extensions/xep-0124.xml
+++ b/extensions/xep-0124.xml
@@ -353,7 +353,7 @@ Content-Length: 104
<ul>
<li><strong>'sid'</strong> -- This attribute specifies the SID</li>
<li><strong>'wait'</strong> -- This is the longest time (in seconds)
that the connection manager will wait before responding to any request during
the session. The time MUST be less than or equal to the value specified in the
session request.</li>
- <li><strong>'hold'</strong> -- This attribute informs the client about
the maximum number of requests the connection manager will keep waiting at any
one time during the session. This value MUST NOT be greater than the value
specified by the client in the session request.</li>
+ <li><strong>'requests'</strong> -- This attribute enables the
connection manager to limit the number of simultaneous requests the client
makes (see <link url="#overactive">Overactivity</link> and <link
url="#poll">Polling Sessions</link>). This value must be larger than the 'hold'
attribute value specified in the session request. The RECOMMENDED value is one
more than the value of the 'hold' attribute specified in the session
request.</li>
</ul>
<p>The <body/> element SHOULD also include the following
attributes (they SHOULD NOT be included in any other responses):</p>
<ul>
@@ -361,7 +361,6 @@ Content-Length: 104
<li><strong>'polling'</strong> -- This attribute specifies the
shortest allowable polling interval (in seconds). This enables the client to
not send empty request elements more often than desired (see <link
url="#poll">Polling Sessions</link> and <link
url="#overactive">Overactivity</link>).</li>
<li><strong>'inactivity'</strong> -- This attribute specifies the
longest allowable inactivity period (in seconds). This enables the client to
ensure that the periods with no requests pending are never too long (see <link
url="#poll">Polling Sessions</link> and <link
url="#inactive">Inactivity</link>).</li>
<li><strong>'hold'</strong> -- This attribute informs the client about
the maximum number of requests the connection manager will keep waiting at any
one time during the session. This value MUST NOT be greater than the value
specified by the client in the session request.</li>
- <li><strong>'requests'</strong> -- This attribute enables the
connection manager to limit the number of simultaneous requests the client
makes (see <link url="#overactive">Overactivity</link> and <link
url="#poll">Polling Sessions</link>). This value must be larger than the 'hold'
attribute value specified in the session request. The RECOMMENDED value is one
more than the value of the 'hold' attribute specified in the session
request.</li>
<li><strong>'to'</strong> -- This attribute communicates the identity
of the backend server to which the client is attempting to connect.</li>
</ul>
<p>The connection manager MAY include an <strong>'accept'</strong>
attribute in the session creation response element, to specify a
comma-separated list of the content encodings it can decompress. After
receiving a session creation response with an 'accept' attribute, clients MAY
include an HTTP Content-Encoding header in subsequent requests (indicating one
of the encodings specified in the 'accept' attribute) and compress the bodies
of the requests accordingly.</p>
--
1.8.5.2
