16 Facts About XMPP


Unlike most commercial instant messaging protocols, XMPP is defined in an open standard in the application layer.

FactSnippet No. 687,633

The architecture of the XMPP network is similar to email; anyone can run their own XMPP server and there is no central master server.

FactSnippet No. 687,634

Original and "native" transport protocol for XMPP is Transmission Control Protocol, using open-ended XML streams over long-lived TCP connections.

FactSnippet No. 687,635

Since XML is text based, normal XMPP has a higher network overhead compared to purely binary solutions.

FactSnippet No. 687,636

Unlike multi-protocol clients, XMPP provides this access at the server level by communicating via special gateway services running alongside an XMPP server.

FactSnippet No. 687,637

XMPP is implemented by many clients, servers, and code libraries.

FactSnippet No. 687,638

Several large public IM services natively use or used XMPP, including LiveJournal's "LJ Talk", Nimbuzz, and HipChat.

FactSnippet No. 687,639

XMPP is used in deployments of non-IM services, including smart grid systems such as demand response applications, message-oriented middleware, and as a replacement for SMS to provide text messaging on many smartphone clients.

FactSnippet No. 687,640

Some largest messaging providers use, or have been using, various forms of XMPP based protocols in their backend systems without necessarily exposing this fact to their end users.

FactSnippet No. 687,641

XMPP is the de facto standard for private chat in gaming related platforms such as Origin, and PlayStation, as well as the now discontinued Xfire and Raptr.

FactSnippet No. 687,642

Internet Engineering Task Force formed an XMPP working group in 2002 to formalize the core protocols as an IETF instant messaging and presence technology.

FactSnippet No. 687,643

The early Jabber protocol, as developed in 1999 and 2000, formed the basis for XMPP as published in RFC 3920 and RFC 3921 in October 2004 .

FactSnippet No. 687,644

The XMPP Working group produced specifications RFC 3922 and RFC 3923.

FactSnippet No. 687,645

Several XMPP extensions are part of the experimental implementation: Efficient XML Interchange Format; Sensor Data; Provisioning; Control; Concentrators; Discovery.

FactSnippet No. 687,646

IETF XMPP working group has produced a series of Request for Comments documents:.

FactSnippet No. 687,647

XMPP has often been regarded as a competitor to SIMPLE, based on Session Initiation Protocol, as the standard protocol for instant messaging and presence notification.

FactSnippet No. 687,648