I am curious about your recommendation not use use REST in production, and
your comment "REST can lead to dropped messages." ActiveMQ has seen a lot
of growth in the last few years; I'm wondering if the situation has changed
since then.
Here's some background about my use case:
I represent a vend
Allow me to clarify. First, perhaps my statement is a little stronger than
it should be - I wouldn't use it, but I can see it being used.
Here's my reasoning:
* REST and JMS protocols are notably different; REST is
one-message-per-connection while JMS is many-messages-per-connnection
* JMS subsc
When I read "http://activemq.apache.org/rest.html";, I don't see anything saying
the REST/HTTP interface should not be used in production code. Please
elaborate, send me, or direct me to a list of your concerns. I understand that
Java clients would want to use the JMS API, but what is so wrong
First off, let me warn that this isn't a "recipe" that I would use;
actually any REST interface for JMS is a nice feature for prototyping, but
not something I would use for production-quality code. Add Topics to that
mix, and it's really concerning.
With that said, your problem may be easy to exp
