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

1.1pre2

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1156 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-08-15 20:59:49 +00:00
parent b357656602
commit ff7e99af40
1 changed files with 27 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
xep-0100.xml
View File

@ -29,10 +29,10 @@
&stpeter;
&dizzyd;
<revision>
<version>1.1pre1</version>
<date>2007-08-10</date>
<version>1.1pre2</version>
<date>2007-08-15</date>
<initials>psa</initials>
<remark>Clarified that username used for registration is legacy user address.</remark>
<remark>Clarified that username used for registration is legacy user address; added optional support for specifying roster group name for contact list items sent via roster item exchange.</remark>
</revision>
<revision>
<version>1.0</version>
@ -961,6 +961,30 @@
</section1>
<section1 topic='Contact Lists' anchor='rosters'>
<p>Some legacy services maintain server-side contact lists, which are sent to the gateway when it logs in to the legacy service on behalf of the user. The gateway MAY initiate adding of the legacy contact list items to the user's Jabber roster. Some existing gateways do this by sending a presence stanza of type "subscribed" from the legacy contact's JID (e.g., &lt;LegacyUser@gateway.jabberserver.com&gt;) to the Jabber user; unfortunately, this behavior violates the presence stanza handling rules specified in <cite>RFC 3921</cite>. Therefore, a gateway SHOULD instead send the legacy contact list items to the Jabber User via the &xep0144; protocol.</p>
<p>In order to inform the gateway of the user's desired roster group for the contacts to be sent, the user's client MAY include a field of "group" in the data form it sends when registering with the gateway (if the gateway provides a data form in the registration requirements stanza).</p>
<example caption="User Provides Registration Information"><![CDATA[
<iq type='set'
from='romeo@montague.net/orchard'
to='aim.shakespeare.lit'
id='reg2'>
<query xmlns='jabber:iq:register'>
<x xmlns='jabber:x:data' type='submit'>
<field var='FORM_TYPE'>
<value>jabber:iq:register</value>
</field>
<field var='username'>
<value>RomeoMyRomeo</value>
</field>
<field var='password'>
<value>ILoveJuliet</value>
</field>
<field var='group'>
<value>AIM (Work)</value>
</field>
</x>
</query>
</iq>
]]></example>
</section1>
<section1 topic='Business Rules' anchor='bizrules'>
<p>The following business rules apply:</p>