mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-13 12:55:10 -05:00
XEP-0198: the inline feature element should be called 'sm'
as per XSF room discussion on September 11
This commit is contained in:
parent
31779d952b
commit
98619addb2
@ -570,7 +570,7 @@
|
||||
</section3>
|
||||
</section2>
|
||||
<section2 topic="Inline Stream Resumption" anchor="inline-resume">
|
||||
<p>To indicate support for inlining stream resumption into the authentication process, the server adds a <resume/> element in the namespace "urn:xmpp:sm:3" to the <inline/> element of SASL2.</p>
|
||||
<p>To indicate support for inlining stream resumption into the authentication process, the server adds a <sm/> element in the namespace "urn:xmpp:sm:3" to the <inline/> element of SASL2.</p>
|
||||
<p>If the client wishes to resume an existing session it, it simply includes the <resume/> element defined by this specification in the SASL2 <authenticate/> element.</p>
|
||||
<p class="box">Note: If the client included a <resume/> element in its SASL2 <authenticate/> element, that MUST be processed first by the server. If that resumption is successful, the server MUST skip resource binding (a resumed session already has a resource bound) and MUST entirely ignore the <bind/> request that might also be inlined in the <authenticate/> element.</p>
|
||||
<p>&xep0388; mandates that the <success> element is immeditaly followed by stream features. If a former stream has been successfully resumed using this specification, the stream is considered re-established immediately after the <success/> element instead and stream features MUST NOT be sent in this case.</p>
|
||||
|
Loading…
Reference in New Issue
Block a user