Looks like the mailing lists have been having some issues over the last 36 hours or so... so sending this response that seems to have disappeared into the ether...
On 21 March 2017 at 09:04, Rob Godfrey <[email protected]> wrote: > Hi Dan, > > You are correct - the existing features were essentially aimed at > management/support operations (deleting messages from a queue), with the > enqueing feature being added to support a particular use case (brokers > sitting inside a firewall which only let through HTTP, and did not allow > WebSocket connections, needing low volume message ingress from outside that > firewall). > > In terms of a more general messaging API over REST, the questions I was > debating with myself were to what extent the API should be "AMQP"-like > (with the notion that we might want to try to establish some sort of > standard way of doing AMQP over REST... e.g. first you PUT a "consumer" > object, then you interact with that) and, somewhat related, what format the > messages should be in (the existing API allows for messages to be sent in a > JSON format rather than the binary AMQP message). What are your thoughts > on this? > > -- Rob > > On 21 March 2017 at 06:14, Dan Langford <[email protected]> wrote: > >> I am going through the HTTP API documentation and I just want to confirm >> what I am seeing. Is there a portion of the API to enqueue and dequeue >> messages via HTTP? I was hoping for some REST api like Google's TaskQueues >> <https://cloud.google.com/appengine/docs/standard/java/taskqueue/rest/> >> that >> include a "lease", "delete", and "insert" operations. Or maybe something >> like Amazon SQS >> <http://docs.aws.amazon.com/AWSSimpleQueueService/latest/API >> Reference/API_Operations.html>with >> actions "ReceiveMessage", "DeleteMessage", and "SendMessage". Or >> Microsoft ServiceBus >> <https://docs.microsoft.com/en-us/rest/api/servicebus/send-message>or >> ActiveMQ <http://activemq.apache.org/rest.html>, or HornetQ >> <https://docs.jboss.org/hornetq/2.2.2.Final/rest-interface- >> manual/html_single/#d0e163> >> . >> >> In the current QPID API I can see the ability to get the contents of a >> message and delete but these seems very administrative and not intended >> for >> general messaging. Am I missing something or is this just a feature that >> does not exist? If its truly needed I can throw together a shim unless any >> of you know of an existing one. >> >> Thanks so much >> > >
