activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: STOMP Vs RESTful to consume incoming messages
Date Tue, 06 Sep 2011 09:19:22 GMT
Hi Ravi,

the general recommendation is Stomp as it's more "messaging-oriented"
protocol than REST. With Stomp you can use all semantics important for
asynchronous messaging like transactions, various types of acknowledgment
modes and such. Also, the protocol is easy enough http-like so there are a
lot of clients for it already in many languages.

Regards
-- 
Dejan Bosanac - http://twitter.com/dejanb
-----------------
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Tue, Sep 6, 2011 at 12:10 AM, Ravi Julapalli <julaboy@yahoo.com> wrote:

> Hi,
> I am working on a new project that requires us to consume incoming messages
> over ActiveMQ
> The application consuming messages is a web app built in PHP.
>
> The recommendation of our solutions architect is to use STOMP for
> retrieving messages.
> I read through docs and understand that ActiveMQ does provide REST
> interfaces to consume messages.
> However I am not fully sure of what advantages REST might have over STOMP
> and vice versa.
>
> I will greatly appreciate if someone can provide a bit more information for
> us to be able to make a informed decision.
>
> best regards,
> Ravi
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message