moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-25 02:32:18 -05:00
Code Issues Releases Wiki Activity

corrected example

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2590 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-12-19 22:49:57 +00:00
parent d7af7570b9
commit 778a161f1d
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
xep-0205.xml
View File

@ -90,18 +90,18 @@
<p>If an entity attempts to connect but the maximum number of connections has been reached, the receiving server MUST NOT allow the new connection to proceed. There are no XMPP errors associated with this behavior, since it occurs at the binding (TCP or HTTP) level before an XML stream is initiated.</p> <p>If an entity attempts to connect but the maximum number of connections has been reached, the receiving server MUST NOT allow the new connection to proceed. There are no XMPP errors associated with this behavior, since it occurs at the binding (TCP or HTTP) level before an XML stream is initiated.</p>
</section2> </section2>
<section2 topic='Unauthenticated Connections' anchor='rec-auth'> <section2 topic='Unauthenticated Connections' anchor='rec-auth'>
<p>In accordance with <cite>RFC 3920</cite>, a server MUST NOT process XML stanzas from clients that have not provided appropriate authentication credentials, and MUST NOT process XML stanzas from peer servers whose identity it has not either authenticated via SASL (see &rfc4422;) or verified via server dialback.</p> <p>In accordance with <cite>RFC 3920</cite>, a server MUST NOT process XML stanzas (i.e., &MESSAGE;, &PRESENCE;, or &IQ;) from clients that have not provided appropriate authentication credentials, and MUST NOT process XML stanzas from peer servers whose identity it has not either authenticated via SASL (see &rfc4422;) or verified via server dialback.</p>
</section2> </section2>
<section2 topic='Simultaneous Resources' anchor='rec-resources'> <section2 topic='Simultaneous Resources' anchor='rec-resources'>
<p>A server implementation SHOULD enable a server administrator to limit the number of resources it will allow an account to bind at any one time.</p> <p>A server implementation SHOULD enable a server administrator to limit the number of resources it will allow an account to bind at any one time.</p>
<p>If a connected client attempts to bind a resource but has already reached the configured number of allowable resources, the receiving server MUST return a &notallowed; stanza error, which in turn SHOULD include an application-specific error condition of &lt;resource-limit-exceeded/&gt;, as shown in the following example:</p> <p>If a connected client attempts to bind a resource but has already reached the configured number of allowable resources, the receiving server MUST return a &constraint; stanza error, which in turn SHOULD include an application-specific error condition of &lt;resource-limit-exceeded/&gt;, as shown in the following example:</p>
<example caption='Resource number limit violation'><![CDATA[ <example caption='Resource number limit violation'><![CDATA[
<iq type='error' id='bind_2'> <iq type='error' id='bind_2'>
<bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'> <bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'>
<resource>someresource</resource> <resource>someresource</resource>
</bind> </bind>
<error type='modify'> <error type='cancel'>
<not-allowed xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/> <resource-constraint xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
<resource-limit-exceeded xmlns='http://jabber.org/protocol/errors'/> <resource-limit-exceeded xmlns='http://jabber.org/protocol/errors'/>
</error> </error>
</iq> </iq>