moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 08:45:04 -05:00
Code Issues Releases Wiki Activity

1.2pre1

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2152 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-08-14 19:15:32 +00:00
parent 9364280a10
commit 317c68ba52
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-0174.xml
View File

@ -26,6 +26,12 @@
<shortname>linklocal</shortname>
<registry/>
&stpeter;
<revision>
<version>1.2pre1</version>
<date>in progress, last updated 2008-08-14</date>
<initials>psa</initials>
<remark><p>Clarified handling of stream closes.</p></remark>
</revision>
<revision>
<version>1.1</version>
<date>2008-03-05</date>
@ -391,11 +397,12 @@ juliet IN TXT "ver=66/0NaeaBKkwk85efJTGmU47vXI="
<example caption="Ending the Chat"><![CDATA[
</stream:stream>
]]></example>
<p>The other party then closes the stream in the other direction as well:</p>
<p>The other party MUST then also close the stream in the other direction:</p>
<example caption="Closing the Stream"><![CDATA[
</stream:stream>
]]></example>
<p>Both parties then MUST close the TCP connection between them.</p>
<p>The closing party (i.e., the party that sent the first closing stream tag) then MUST close the TCP connection between them.</p>
<p>Note: The closing party might receive additional stanzas from the other party after sending its closing stream tag and before receiving a closing stream tag from the other party (e.g., because of network latency or because the other party has messages queued up for delivery when it receives the closing party's closing stream tag). Therefore, the closing party needs to be prepared to handle such messages, which it SHOULD do by presenting them to the controlling user (if any).</p>
</section1>
<section1 topic='Going Offline' anchor='offline'>