P
PhilF
Guest
Thanks. Our spec matches the REST / web services model; there is a certain amount of error checking that is done on each call -- so a response is required. Their JMS replacement design involves two queues - one for input and one for output. I had thought that ActiveMQ would simply act as middleware -- providing a reliable way of passing messages, handling the queue/retry. (Does STOMP to MQ manage the retries?) For our REST calls to them, I would still have to queue and retry. (Which to me means that there is no point in going through ActiveMQ for these.) But can't ActiveMQ make REST calls to us, and manage the retry on failure?
Continue reading...
Continue reading...