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

Windows Live Messenger 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1092 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-07-20 20:11:37 +00:00
parent 3fc958fdf3
commit f27ddbef04
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
xep-0100.xml
View File

@ -96,7 +96,7 @@
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
<p>One distinguishing characteristic of Jabber technologies from their earliest days has been the existence of gateways (also called "transports") between the Jabber network and legacy instant messaging services such as AOL Instant Messenger (AIM), ICQ, MSN Messenger, and Yahoo! Messenger. Surprisingly, the recommended behavior of such gateways, including the protocol elements used by a client to interact with a gateway, has never been fully documented. This document attempts to fill that void by codifying best practices for gateway interaction.</p>
<p>One distinguishing characteristic of Jabber technologies from their earliest days has been the existence of gateways (also called "transports") between the Jabber network and legacy instant messaging services such as AOL Instant Messenger (AIM), ICQ, Windows Live Messenger, and Yahoo! Messenger. Surprisingly, the recommended behavior of such gateways, including the protocol elements used by a client to interact with a gateway, has never been fully documented. This document attempts to fill that void by codifying best practices for gateway interaction.</p>
<p>Note well that this document defines protocol usage with regard to client proxy gateways, i.e., gateways that "masquerade" as a client on a non-Jabber IM service. Gateways that perform direct protocol translation without proxying for an account on a non-Jabber service are not addressed in this document. Furthermore, this document does not define any interaction between a gateway and the non-Jabber service, only interactions between a Jabber client and the gateway. Although what happens on the other side of the gateway is highly dependent on the nature of the legacy service, gateways should at least provide a common interface on the Jabber side of the gateway so that Jabber clients can be written in a consistent fashion.</p>
</section1>
<section1 topic='Glossary' anchor='glossary'>
@ -896,7 +896,7 @@
Please enter the AOL Screen Name of the
person you would like to contact.
</desc>
<prompt>Screen Name</prompt>
<prompt>Contact ID</prompt>
</query>
</iq>
]]></example>
@ -911,25 +911,25 @@
<tr>
<td>AOL Instant Messenger</td>
<td>gateway/aim</td>
<td>AOL Screen Name</td>
<td>Contact ID</td>
<td>Please enter the AOL Screen Name of the person you would like to contact.</td>
</tr>
<tr>
<td>ICQ</td>
<td>gateway/icq</td>
<td>ICQ Number</td>
<td>Contact ID</td>
<td>Please enter the ICQ Number of the person you would like to contact.</td>
</tr>
<tr>
<td>MSN Messenger</td>
<td>gateway/msn</td>
<td>MSN Address</td>
<td>Please enter the MSN Address of the person you would like to contact.</td>
<td>Windows Live Messenger</td>
<td>gateway/msn <note>The service discovery type was originally defined as "msn" to reflect the name of the service as "MSN Messenger"; this type is retained even though the service has been renamed to "Windows Live Messenger".</note></td>
<td>Contact ID</td>
<td>Please enter the Windows Live Messenger address of the person you would like to contact.</td>
</tr>
<tr>
<td>Yahoo! Messenger</td>
<td>gateway/yahoo</td>
<td>Yahoo ID</td>
<td>Contact ID</td>
<td>Please enter the Yahoo ID of the person you would like to contact.</td>
</tr>
</table>