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

Update to Address Dave Cridland comments

Browse Source
This commit is contained in:
Steve Kille 2015-07-17 17:58:34 +01:00 committed by Matthew A. Miller
parent 4b3918acac
commit 1936c1c4b7
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
xep-0361.xml
View File

@ -31,6 +31,12 @@
<email>steve.kille@isode.com</email> <email>steve.kille@isode.com</email>
<jid>steve.kille@isode.com</jid> <jid>steve.kille@isode.com</jid>
</author> </author>
<revision>
<version>0.2</version>
<date>2015-07-18</date>
<initials>sek</initials>
<remark><p>Assume an open &lt;stream:stream&gt;, implicitly parenting all XML elements received and sent.</p></remark>
</revision>
<revision> <revision>
<version>0.1</version> <version>0.1</version>
<date>2015-07-16</date> <date>2015-07-16</date>
@ -71,7 +77,7 @@ The solution set out here is to eliminate all the intial handshaking and to star
In simple terms, this can be considered as operation of RFC 6121 communication between a pair of XMPP servers without the preliminary negotiation done in RFC 6120. It might be considered that the start point is the In simple terms, this can be considered as operation of RFC 6121 communication between a pair of XMPP servers without the preliminary negotiation done in RFC 6120. It might be considered that the start point is the
DONE box in Figure 3 of RFC 6121. The TCP connection is opened and messages start to flow, as if the preceding RFC 6120 exchanges had taken place. All configuration informaition, including choice of port is handled by the a priori configuration.</p> DONE box in Figure 3 of RFC 6121. The TCP connection is opened and messages start to flow, as if the preceding RFC 6120 exchanges had taken place. All configuration informaition, including choice of port is handled by the a priori configuration.</p>
<p> <p>
Note that stream open is not sent. The interaction takes place as if this had completed. Note that stream open is not sent. The interaction takes place as if this had completed. All XML elements received over the stream are treated as if they were inside a normal S2S stream that has been opened with the following stream opening tag, defining the default namespace of jabber:server and the stream namespace of &lt;stream:stream xmlns:stream='...' xmlns='...'&gt;. When a stream is closed, a stream close SHOULD be exchanged.
</p> </p>
</section2> </section2>