moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

tmp namespace 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1626 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-01-30 21:28:32 +00:00
parent b31cb56a81
commit 183fa58062
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
xep-0225.xml
View File

@ -63,7 +63,7 @@
</section1>
<section1 topic='Hostname Binding' anchor='bind'>
<p>The protocol defined in <cite>XEP-0114</cite> depended on use of the 'to' address in the stream header to specify the hostname of the component. By contrast, client-to-server connections use stream establishment is followed by binding of a resource to the stream (in fact multiple resources can be bound to the stream). This protocol emulates client-to-server connections by using a hostname binding process that is similar to the resource binding process specified in XMPP Core.</p>
<p>If a server offers component binding over a stream, it MUST advertise a feature of "http://www.xmpp.org/extensions/xep-xxxx.html#ns".</p>
<p>If a server offers component binding over a stream, it MUST advertise a feature of "urn:xmpp:tmp:component".</p>
<example caption='Stream Feature'><![CDATA[
S: <stream:stream
from='example.com'
@ -75,7 +75,7 @@ S: <stream:stream
xmlns:stream='http://etherx.jabber.org/streams'>
S: <stream:features>
<bind xmlns='http://www.xmpp.org/extensions/xep-xxxx.html#ns'>
<bind xmlns='urn:xmpp:tmp:component'>
<required/>
</bind>
</stream:features>
@ -83,7 +83,7 @@ S: <stream:features>
<p>In order to bind a hostname, the component sends a bind request to the server.</p>
<example caption='Bind Request'><![CDATA[
C: <iq id='bind_1' type='set'>
<bind xmlns='http://www.xmpp.org/extensions/xep-xxxx.html#ns'>
<bind xmlns='urn:xmpp:tmp:component'>
<hostname>chat.example.com</hostname>
</bind>
</iq>
@ -95,7 +95,7 @@ S: <iq id='bind_1' type='result'/>
<p>A component can send a subsequent bind request to bind another hostname (a server MUST support binding of multiple hostnames).</p>
<example caption='Another Bind Request'><![CDATA[
C: <iq id='bind_2' type='set'>
<bind xmlns='http://www.xmpp.org/extensions/xep-xxxx.html#ns'>
<bind xmlns='urn:xmpp:tmp:component'>
<hostname>foo.example.com</hostname>
</bind>
</iq>
@ -104,7 +104,7 @@ C: <iq id='bind_2' type='set'>
<p>A component can also unbind a resource that has already been bound (a server MUST support unbinding).</p>
<example caption='Unbind Request'><![CDATA[
C: <iq id='unbind_1' type='set'>
<unbind xmlns='http://www.xmpp.org/extensions/xep-xxxx.html#ns'>
<unbind xmlns='urn:xmpp:tmp:component'>
<hostname>foo.example.com</hostname>
</unbind>
</iq>
@ -125,7 +125,7 @@ S: <iq id='unbind_1' type='result'/>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='ns'>
<p>Until this specification advances to a status of Draft, its associated namespace shall be "http://www.xmpp.org/extensions/xep-xxxx.html#ns"; upon advancement of this specification, the &REGISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.</p>
<p>Until this specification advances to a status of Draft, its associated namespace shall be "urn:xmpp:tmp:component"; upon advancement of this specification, the &REGISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.</p>
</section2>
</section1>
<section1 topic='XML Schema' anchor='schema'>
@ -134,8 +134,8 @@ S: <iq id='unbind_1' type='result'/>
<xs:schema
xmlns:xs='http://www.w3.org/2001/XMLSchema'
targetNamespace='http://www.xmpp.org/extensions/xep-xxxx.html#ns'
xmlns='http://www.xmpp.org/extensions/xep-xxxx.html#ns'
targetNamespace='urn:xmpp:tmp:component'
xmlns='urn:xmpp:tmp:component'
elementFormDefault='qualified'>
<xs:element name='bind'>