Xmpp Vs Websocket

java websocket xmpp real-time near-real-time
Khafaga picture Khafaga · Oct 24, 2014 · Viewed 28.6k times · Source

I'm about to develop a website that has near real time chat. I know that it can be implemented using xmpp or websocket protocols. I know also that the xmpp protocol has been developed in 1999 , and I guess it should be mature nowadays .On the other hand , the websocket protocol has been developed in 2011.

  1. What was the need for websocket if xmpp was good in handling real time conversations?
  2. What are the major differences between the 2 protocols?
  3. And when should I choose one of them over the other?

Answer

Kev picture Kev · Oct 25, 2014

The short answer is 'both'.

XMPP is a set of application protocol for doing real-time chat (and many other things, for that matter) - it then has to be transported across the network somehow, so you need a transport binding. There are three main transport bindings for XMPP -

  1. TCP/IP, which is what one usually uses on the Internet with native clients on devices
  2. HTTP (called BOSH), which is what one has traditionally used when using XMPP in the browser (as TCP-IP isn't available to Javascript apps in the browser)
  3. Websockets, which is one one uses when doing XMPP in a modern browser.

So if you're developing a chat application in a browser, you'd choose XMPP as the application protocol and you'd use websockets (in a modern browser) or BOSH (in an older browser) as the network transport. If you use an XMPP library for Javascript like Stanza.io (https://github.com/otalk/stanza.io), it'll support both and you'll just be thinking about 'XMPP' rather than the transport layer, other than at setup when you have to tell it what endpoint to connect to.

(You can't use 'just websockets' for chat - you can use websockets without XMPP, but what this really means is that you're inventing your own application-layer protocol for chat, and the odds are you're going to save a lot of time and headaches by taking advantage of the work that's already gone into writing one with useful properties (security, identity, extensibility etc.) and for which there are existing libraries and servers by going XMPP instead.)

Related questions

javax.websocket client simple example

Can someone please provide me very simple example of websocket client using javax.websocket? I want to connect to websocket (ws://socket.example.com:1234), send message (add channel) and listen to messages. All messages (sent & listened) are in JSON …

Read More
websocket closing connection automatically

I'm building an application in java that has an embedded websocket server based on jetty. The client is the default websocket implementation in google chrome. Everything is working ok, only if there is no transfer between server and client after …

Read More
I get a status 200 when connecting to the websocket, but it is an error?

My error shows up in the console of my browser: "WebSocket connection to 'ws://localhost:32768/DspClusterWebServices/myHandler' failed: Unexpected response code: 200" I am using Spring Websockets 4.1.5 and Tomcat 8.0.18. My WebSocketConfigurer implementation class looks like: @Configuration @Controller @EnableWebSocket public class WebSocketConfig …

Read More