QLPUSHTIMER command

[mc0]

The QLPUSHTIMER command would allow adding an event that should run after an elapsed number of seconds (waitDuration). This isn't a guaranteed contract except when the consumer sends the TIMER option to QRPOP command which will ensure all events have met their waitDuration before returning them.

Events in the same queue are expected to have the same waitDuration to maintain simple checks.

+QLPUSHTIMER queue eventID waitDuration contents
-QRPOP queue [EX seconds] [UNSAFE]
+QRPOP queue [EX seconds] [UNSAFE] [TIMER]

[mediocregopher]

I'm not totally sold on this feature, it seems like an odd thing to put in a queue. At the same time I understand why it'd be useful. I think we should try this out but be careful with how much complexity it's going to add to the codebase, I get the feeling it might not be worth it.

Also, if we do go forward with this, I think instead of TIMER we should instead make it WAIT. It's a little more clear what's actually going to happen. So the api would look like:

QLPUSHWAIT queue eventID waitDuration contents
QRPOP queue [EX seconds] [UNSAFE] [WAIT]

Maybe we should think about not even making a new push command? Maybe something like:

QLPUSH queue eventID contents [WAIT waitDuration]

Fewer commands is better, but more complex commands is worse, so I'm not sure of it. What do you think?