QBLPUSH and QBRPUSH commands

[mc0]

The QBLPUSH and QBRPUSH commands would allow blocking until some timeout is met and receiving all messages related to that eventID. This would be achieved by listening on the QueueChannelNameKey(queueName, eventID) redis subscription channel. QREM would need to be modified to allow passing in a result string of data that publishes to that same channel.

+QBLPUSH queue eventID timeout contents
+QBRPUSH queue eventID timeout contents

[mediocregopher]

So would the client be listening on that redis channel? Or were you just saying it should do that internally?

I would think QBLPUSH and QBRPUSH would return either nil or whatever data is passed back by the QREM call (and nil on timeout). We also might think about renaming QREM, since it's job isn't really to remove items from the queue, but more to acknowledge that they've been consumed correctly and shouldn't be given out again, and sending back a result string to a "remove"-type command would be really strange.

As with #7 maybe we could just make this part of the QLPUSH and QRPUSH commands? Something like:

QLPUSH queue eventID contents [BLOCK blockTimeout]

Again, not sure which is the better approach, but it's and idea.