Cometd vs ActiveMQ for server-side downloads for real-time web applications

Question

We have a requirement to develop server side push infra for real-time web applications. For this, I am considering using Cometd, as it supports both long polling and socket-based implementations.

However, I recently came across links like http://activemq.apache.org/ajax.html and http://activemq.apache.org/websockets.html which say that even ActiveMQ provides server-side support using a long survey (Comet technique) as well as web sockets. I understand that the ActiveMQ implementation for this does not comply with the Bayeux protocol.

Are there any advantages / benefits of ActiveMQ over Cometd for server side solutions? Are there any additional features provided by one of them? What is more popular and stable?

Thanks Deepak

Answer 1

I would say that the main reason for choosing ActiveMQ is when you create the backend technology based on messaging in the first place. Then you can very easily get up and work by clicking messages in browsers.

However, I really don't believe that ActiveMQ really was built into the glue technology between the backend and front-end, so it can be a weird bird to fit into the general case (although I have to admit that I haven't tried).