moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-28 12:12:22 -05:00
Code Issues Releases Wiki Activity

0.21

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1420 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-11-27 19:37:41 +00:00
parent 6f67dc4cfa
commit 15d1f6bf57
1 changed files with 36 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
xep-0166.xml
View File

@ -26,6 +26,12 @@
&robmcqueen; &robmcqueen;
&seanegan; &seanegan;
&hildjj; &hildjj;
<revision>
<version>0.21</version>
<date>2007-11-27</date>
<initials>psa</initials>
<remark><p>Further editorial review.</p></remark>
</revision>
<revision> <revision>
<version>0.20</version> <version>0.20</version>
<date>2007-11-15</date> <date>2007-11-15</date>
@ -295,7 +301,7 @@ Romeo Juliet
</jingle> </jingle>
</iq> </iq>
]]></example> ]]></example>
<p>The initiator then acknowledges the session-accept message.</p> <p>The initiator then acknowledges the session-accept action.</p>
<example caption="Initiator acknowledges session-accept"><![CDATA[ <example caption="Initiator acknowledges session-accept"><![CDATA[
<iq from='romeo@montague.lit/orchard' <iq from='romeo@montague.lit/orchard'
id='accept1' id='accept1'
@ -392,7 +398,7 @@ Romeo Juliet
<p>At the most basic level, the process for negotiating a Jingle session is as follows:</p> <p>At the most basic level, the process for negotiating a Jingle session is as follows:</p>
<ol> <ol>
<li>One user (the "initator") sends to another user (the "responder") a session request with at least one content type.</li> <li>One user (the "initator") sends to another user (the "responder") a session request with at least one content type.</li>
<li>If the responder wants to proceed, it provisionally accepts the request by sending an IQ result.</li> <li>If the responder wants to proceed, it acknowledges the session initiation request by sending an IQ result.</li>
<li>Both the initiator and responder start exchanging possible transport candidates as quickly as possible (these are sent in quick succession before further negotiation in order to minimize the time required before media data can flow).</li> <li>Both the initiator and responder start exchanging possible transport candidates as quickly as possible (these are sent in quick succession before further negotiation in order to minimize the time required before media data can flow).</li>
<li>These candidates are checked for connectivity.</li> <li>These candidates are checked for connectivity.</li>
<li>As soon as the responder finds a candidate over which media can flow, the responder sends to the initiator a "session-accept" action.</li> <li>As soon as the responder finds a candidate over which media can flow, the responder sends to the initiator a "session-accept" action.</li>
@ -768,6 +774,7 @@ PENDING o---------------------+ |
</query> </query>
</iq> </iq>
]]></example> ]]></example>
<p>Naturally, support MAY also be determined via the dynamic, presence-based profile of Service Discovery defined in <cite>XEP-0115</cite>.</p>
</section1> </section1>
<section1 topic='Conformance by Using Protocols' anchor='conformance'> <section1 topic='Conformance by Using Protocols' anchor='conformance'>