Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EUG:Introduction to XMPP"

(Properties)
(Properties)
Line 14: Line 14:
  
 
==Properties==
 
==Properties==
* standardized <br/>The XMPP specifications are publicly available. The IETF has also formally adopted the basic protocols as instant messaging and presence technology and published as RFC3920 and RFC3921.  
+
* standardized <br/>The XMPP specifications are publicly available. The IETF has also formally adopted the basic protocols as instant messaging and presence technology and published these as RFC3920 and RFC3921.  
 
* proven <br/>The specification of XMPP since 1998 more and more stabilized. Meanwhile, hundreds of developers working with XMPP servers and tens of thousands of millions of users use it.  
 
* proven <br/>The specification of XMPP since 1998 more and more stabilized. Meanwhile, hundreds of developers working with XMPP servers and tens of thousands of millions of users use it.  
 
* expandable <br/>The protocol uses XML namespaces. This way everyone can extend the protocol without disturbing existing applications.   
 
* expandable <br/>The protocol uses XML namespaces. This way everyone can extend the protocol without disturbing existing applications.   
 
* decentralized <br/>A large number of servers woven together into one large network.  
 
* decentralized <br/>A large number of servers woven together into one large network.  
 
* safe <br/>Robust security with SASL and TLS are supported.
 
* safe <br/>Robust security with SASL and TLS are supported.

Revision as of 13:41, 11 June 2012

Introduction to XMPP

XMPP stands for eXtensible Messaging and Presence Protocol. It is an open XML based network protocol standard for instant messaging and presence notification. The XMPP protocol is used by many applications under which Google Talk.

When two users want to talk to each other the protocol takes the following form:

Suppose juliet@capulet.com wants to chat with romeo@montague.net. Juliet and Romeo, respectively, have an account on the servers capulet.com and montague.net. If Juliet wants to send a message to Romeo the following occurs:

  1. Juliet XMPP client sends the message to the XMPP server capulet.com.
  2. If montague.net is blocked on capulet.com, then the message is discarded.
  3. The capulet.com XMPP server opens a connection to the XMPP server montague.net.
  4. The montague.net server sends the message to Romeo's XMPP client.
  5. If capulet.com is blocked on montague.net, then the message is removed.
  6. If Romeo is not connected, then the message is stored until Romeo comes back online. (Assuming that the server allows offline messages.)
  7. Romeo receives the message.

Properties

  • standardized
    The XMPP specifications are publicly available. The IETF has also formally adopted the basic protocols as instant messaging and presence technology and published these as RFC3920 and RFC3921.
  • proven
    The specification of XMPP since 1998 more and more stabilized. Meanwhile, hundreds of developers working with XMPP servers and tens of thousands of millions of users use it.
  • expandable
    The protocol uses XML namespaces. This way everyone can extend the protocol without disturbing existing applications.
  • decentralized
    A large number of servers woven together into one large network.
  • safe
    Robust security with SASL and TLS are supported.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.