Stomp is a great protocol for a few simple reasons.
1. It is Human Readable and incredibly simple to implement (a reasonable parser might be 20-100 lines depending on your language)
2. Stomp clients already exist in 14 different languages, including Java, C#, Python, Ruby, Perl, PHP, and JavaScript.
3. There are an increasing number of servers/brokers that support Stomp; it is the most widely inter-operable MQ protocol at this point, with support in at least five servers.
4. Stomp clients can easily consume JMS via ActiveMQ or StompConnect, and easily consume AMQP via RabbitMQ.
5. Writing a light-weight Stomp server is not prohibitively difficult. (such as MorbidQ). This type of server is great for embedding so as to ease development and can generally make life easy for small/medium deployments.
Scalability : XMPP currently suffers from essentially the same redundancy problem also concerning multi-user chat and publish/subscribe services.[7] These too are to be addressed by new protocol extensions.[citation needed] Until deployed, large chatrooms produce a very large amount of overhead.
"rabbiter wraps up in a single, easy to install package many of the pieces necessary to create large decentralized pubsub systems, in a scalable, efficient architecture"
Galago is a desktop presence framework, designed to transmit presence information between programs. To put it in simpler terms, it takes information on who is online and their away/idle states from an instant messenger (such as gaim) or other similar...
“If you enjoyed Kellan Elliott-McCrea and Evan Henshaw-Plath’s presentation “Beyond REST? Building data services with XMPP”, here’s a dose of links.” Excellent list.