问题
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.
- What was the need for websocket if xmpp was good in handling real time conversations?
- What are the major differences between the 2 protocols?
- And when should I choose one of them over the other?
回答1:
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 -
- TCP/IP, which is what one usually uses on the Internet with native clients on devices
- 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)
- 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.)
回答2:
Basically, you are comparing two different things to each other. XMPP is an application protocol while WebSockets is a transport protocol.
I think using XMPP will save you a lot of time. However, you will lose the freedom to implement functionalities the way that suites you best. If your application will use only One-to-one messaging and friend list functions with no clear plan on what you would add in the future, WebSockets + would be a viable solution. On the other hand, if your application will benefit from other XMPP extensions such as Multi-party messaging and Peer-to-peer media sessions it would be better to use XMPP as such functions will require a lot of time to be implemented.
来源：https://stackoverflow.com/questions/26549010/xmpp-vs-websocket