DesignXMPP im » History » Version 2
Anonymous, 02/29/2012 03:32 PM
| 1 | 1 | = Gateway for Instant Messaging= |
|
|---|---|---|---|
| 2 | |||
| 3 | [[TOC(DesignXMPP_im, depth=2)]] |
||
| 4 | |||
| 5 | 2 | In XMPP there are several types of messages which lead to different semantics when exchanging XMPP ''message stanzas'' between 2 endpoints. This section focuses only on message types that allow 2 endpoints to send instant messages to each other. |
|
| 6 | |||
| 7 | Message types: |
||
| 8 | |||
| 9 | * Normal: the default message type. A reply is not expected from the recipient. |
||
| 10 | * Chat: This message type implies both parties have engaged a conversation. |
||
| 11 | * Headline: An endpoint receiving this type of message should never reply, since it's meant to be used by servers or other entities to deliver announcements. |
||
| 12 | |||
| 13 | In SIP there are currently 2 ways of doing Instant Messaging: |
||
| 14 | |||
| 15 | * SIP MESSAGE (RFC 3428) |
||
| 16 | * MSRP (RFC 4975) |
||
| 17 | |||
| 18 | The first one is session-less and the latter is session based. |
||
| 19 | |||
| 20 | The mechanisms described here follow the currently available specifications for SIP-XMPP interoperability: |
||
| 21 | |||
| 22 | * http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-im-01.html |
||
| 23 | * http://xmpp.org/internet-drafts/draft-saintandre-sip-xmpp-chat-03.html |
||
| 24 | |||
| 25 | |||
| 26 | == XMPP single message <-> SIP MESSAGE == |
||
| 27 | |||
| 28 | XMPP single messages are mapped directly to SIP MESSAGE requests and ''vice versa''. |
||
| 29 | |||
| 30 | TODO (image) |