search

iron-io / issues

For Iron.io services issue tracking. Public facing issue tracking for behind the scenes issues.
5 stars 0 forks source link

add the ability the *move* a message from one queue to the other, without requiring POST and DELETE #51

Open rbpasker opened 11 years ago

rbpasker commented 11 years ago

normally, a consumer does GET message from q1 then DELETE message from q1

instead of deleting a message, I would like to move it to another queue, without requiring the consumer to GET/POST/DELETE. instead i would like to GET a message, then POST its unique ID to a second queue, to have it moved from the source queue to a second queue. it is important that the messageID and the other metadata not change so that the consumer can put the the ironMQ message id into a database and track it down later.

two use cases:

  1. i'm processing a message and there's something wrong with it, i would like to put it on another queue so that it can be handled out of band by an exception processing system (which may involve human intervention)
  2. I would like to keep all messages that have been processed so that I can replay them against my app or track down bugs
rbpasker commented 11 years ago

i think this would be especially important for PUSH queues, too, so that the messages don't just disappear, but can be stored for some period of time and then examined or replayed.