Difference between revisions of "Technology overview"

From XMPP WIKI
Jump to navigation Jump to search
(New page: Jabber is an open, secure, spam-free, ad-free, decentralized alternative to consumer IM silos like AOL Instant Messenger, ICQ, Windows Live Messenger, and Yahoo Instant Messenger. Under th...)
 
m
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Jabber is an open, secure, spam-free, ad-free, decentralized alternative to consumer IM silos like AOL Instant Messenger, ICQ, Windows Live Messenger, and Yahoo Instant Messenger. Under the hood, Jabber is a set of streaming XML protocols (called XMPP) that enable any two entities on the Internet to exchange messages, presence, and other structured information in close to real time. Jabber technologies offer several key advantages:
XMPP is an open, secure, spam-free, ad-free, decentralized alternative to consumer IM silos like AOL Instant Messenger, ICQ, Windows Live Messenger, and Yahoo Instant Messenger. Under the hood, XMPP is a set of streaming XML protocols that enable any two entities on the Internet to exchange messages, presence, and other structured information in close to real time. XMPP technologies offer several key advantages:
 
* Open -- the XMPP protocols are free, open, public, and easily understandable; in addition, multiple implementations exist for clients, servers, server components, and code libraries.
    * Open -- the Jabber protocols are free, open, public, and easily understandable; in addition, multiple implementations exist for clients, servers, server components, and code libraries.
* Standard -- the [http://ietf.org/ Internet Engineering Task Force (IETF)] has formalized the core XML streaming protocols as an approved instant messaging and presence technology under the name Extensible Messaging and Presence Protocol or XMPP. The XMPP specifications were published as [http://xmpp.org/rfcs/rfc3920.html RFC 3920] and [http://xmpp.org/rfcs/rfc3921.html RFC 3921] in 2004 and updated in 2011 as [http://xmpp.org/rfcs/rfc6120.html RFC 6120], [http://xmpp.org/rfcs/rfc6121.html RFC 6121] and [http://xmpp.org/rfcs/rfc6122.html RFC 6122], and the [http://xmpp.org/ XMPP Standards Foundation] continues to publish many [http://xmpp.org/xmpp-protocols/xmpp-extensions/ XMPP extensions].
    * Standard -- the Internet Engineering Task Force (IETF) has formalized the core XML streaming protocols as an approved instant messaging and presence technology under the name Extensible Messaging and Presence Protocol or XMPP. The XMPP specifications were published as RFC 3920 and RFC 3921 in 2004, and the XMPP Standards Foundation continues to publish many XMPP extensions.
* Proven -- the first XMPP technologies (Jabber) were developed by Jeremie Miller in 1998 and are now quite stable; hundreds of developers are working on XMPP technologies, there are tens of thousands of XMPP servers running on the Internet today, and millions of people use XMPP for IM.
    * Proven -- the first Jabber technologies were developed by Jeremie Miller in 1998 and are now quite stable; hundreds of developers are working on Jabber technologies, there are tens of thousands of Jabber servers running on the Internet today, and millions of people use Jabber for IM.
* Decentralized -- the architecture of the XMPP network is similar to email; as a result, anyone can run their own XMPP server, enabling individuals and organizations to take control of their IM experience.
    * Decentralized -- the architecture of the Jabber network is similar to email; as a result, anyone can run their own Jabber server, enabling individuals and organizations to take control of their IM experience.
* Secure -- any XMPP server may be isolated from the public XMPP network (e.g., on a company intranet), and robust security using SASL and TLS has been built into the core [http://xmpp.org/xmpp-protocols/rfcs/ XMPP specifications].
    * Secure -- any Jabber server may be isolated from the public Jabber network (e.g., on a company intranet), and robust security using SASL and TLS has been built into the core XMPP specifications.
* Extensible -- using the power of XML namespaces, anyone can build custom functionality on top of the core protocols; to maintain interoperability, common extensions are managed by the [http://xmpp.org/ XMPP Standards Foundation].
    * Extensible -- using the power of XML namespaces, anyone can build custom functionality on top of the core protocols; to maintain interoperability, common extensions are managed by the Jabber Software Foundation.
* Flexible -- XMPP applications beyond IM include network management, content syndication, collaboration tools, file sharing, gaming, and remote systems monitoring.
    * Flexible -- Jabber applications beyond IM include network management, content syndication, collaboration tools, file sharing, gaming, and remote systems monitoring.
* Diverse -- a wide range of companies and open-source projects use the XMPP protocols to build and deploy real-time applications and services; you will never get "locked in" when you use XMPP technologies.
    * Diverse -- a wide range of companies and open-source projects use the Jabber protocols to build and deploy real-time applications and services; you will never get "locked in" when you use Jabber technologies.

Latest revision as of 08:00, 26 August 2011

XMPP is an open, secure, spam-free, ad-free, decentralized alternative to consumer IM silos like AOL Instant Messenger, ICQ, Windows Live Messenger, and Yahoo Instant Messenger. Under the hood, XMPP is a set of streaming XML protocols that enable any two entities on the Internet to exchange messages, presence, and other structured information in close to real time. XMPP technologies offer several key advantages:

  • Open -- the XMPP protocols are free, open, public, and easily understandable; in addition, multiple implementations exist for clients, servers, server components, and code libraries.
  • Standard -- the Internet Engineering Task Force (IETF) has formalized the core XML streaming protocols as an approved instant messaging and presence technology under the name Extensible Messaging and Presence Protocol or XMPP. The XMPP specifications were published as RFC 3920 and RFC 3921 in 2004 and updated in 2011 as RFC 6120, RFC 6121 and RFC 6122, and the XMPP Standards Foundation continues to publish many XMPP extensions.
  • Proven -- the first XMPP technologies (Jabber) were developed by Jeremie Miller in 1998 and are now quite stable; hundreds of developers are working on XMPP technologies, there are tens of thousands of XMPP servers running on the Internet today, and millions of people use XMPP for IM.
  • Decentralized -- the architecture of the XMPP network is similar to email; as a result, anyone can run their own XMPP server, enabling individuals and organizations to take control of their IM experience.
  • Secure -- any XMPP server may be isolated from the public XMPP network (e.g., on a company intranet), and robust security using SASL and TLS has been built into the core XMPP specifications.
  • Extensible -- using the power of XML namespaces, anyone can build custom functionality on top of the core protocols; to maintain interoperability, common extensions are managed by the XMPP Standards Foundation.
  • Flexible -- XMPP applications beyond IM include network management, content syndication, collaboration tools, file sharing, gaming, and remote systems monitoring.
  • Diverse -- a wide range of companies and open-source projects use the XMPP protocols to build and deploy real-time applications and services; you will never get "locked in" when you use XMPP technologies.
Retrieved from "https://wiki.xmpp.org/web/index.php?title=Technology_overview&oldid=7879"