@MSalters Re ‘message queue’: RabbitMQ’s default operation is exactly what you describe: transient pubsub. But with TCP instead of UDP. If you want guaranteed eventual delivery and other persistence and recovery features, then you CAN have that too – it’s an option. That’s the whole point of RabbitMQ and AMQP — you can have lots … Read more
It depends on what you are trying to do and what hardware you are running. MQTT has very low keep-alive traffic. XMPP is a an IM protocol, and has a much, much higher overhead in handling presence messages between all the clients. If you have a small memory footprint constraint, then having to handle the … Read more
It depends what license you can use. Some popular libraries are GPL which can cause serious issues if you need to use it for work, especially if you need to keep proprietary extensions. The LGPL libraries are a little less popular, I think, but you have more flexibility with what you can use them for. … Read more
According to Wikipedia: 5222 TCP XMPP client connection (RFC 6120) Official 5223 TCP XMPP client connection over SSL Unofficial 5269 TCP XMPP server connection (RFC 6120) Official 5298 TCP UDP XMPP JEP-0174: Link-Local Messaging / Official XEP-0174: Serverless Messaging 8010 TCP XMPP File transfers Unofficial The port numbers are defined in RFC 6120 § 14.7.
http://xmpp.org/xmpp-software/libraries/ has a list of software libraries for XMPP. Here is an outdated snapshot of it: ActionScript as3xmpp C iksemel libstrophe Loudmouth C++ gloox Iris oajabber C# / .NET / Mono agsXMPP SDK jabber-net Erlang Jabberlang Flash XIFF Haskell hsxmpp Java Echomine Feridian Jabber Stream Objects (JSO) Smack JavaScript strophe.js xmpp4js Lisp cl-xmpp Objective-C xmppframework … Read more
REST is an architectural style that does not impose a protocol. So yes, you can do REST with Web Sockets, REST with HTTP and REST with FTP if you like. The main reason to use HTTP is that it is easy and fairly simple to communicate with any component or programming language via HTTP and … Read more
contact list (in XMPP this is called a “roster”) Source: XMPP-IM – RFC 6121 § 1.3: Requirements
There is new api now. How does the Messenger Platform work? When a person sends a message to a business on Messenger and as long as this Page uses an app to partially or fully automate conversations, the following will happen. The Facebook server sends webhooks to the URL of the business server, where the … Read more
This is probably way too basic, but at least it’s technical: https://web.archive.org/web/20170916193014/http://www.adarshr.com/fun-with-xmpp-and-google-talk and the second part, https://web.archive.org/web/20171005104211/http://www.adarshr.com:80/fun-with-xmpp-and-google-talk-part-2 It explains what stanzas are, what types are available and stuff.
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 … Read more