226
edits
Difference between revisions of "Technology overview"
Jump to navigation
Jump to search
m
no edit summary
Neustradamus (talk | contribs) m |
Neustradamus (talk | contribs) m |
||
| Line 1: | Line 1: | ||
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: | 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 XMPP 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] | * 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]. | ||
* 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 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. | * 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. | ||