I've seen similar requests on this ML before, but am not aware if any progress is made since. What I am looking for is a method to peek all jobs, like peek and peek-* currently do for a single job. I know it might have drawbacks for heavy usage queues or very fast queues, but I think this is up to the developer to decide. If a peek-all command is load dependent, developers can choose whether or not to use it depending on their own situation.
On the ML others have showed some good use cases why it might come in handy, and I have something similar for myself. My jobs can succeed (and will be deleted) or not. If not, a job might be retried later (e.g. a request to a 3rd party service timed out) or buried (something else happened). I want to use bury because it gives a user the possibility to delete or kick the job. In my case it is often a human being who can decide if a job has to be retried or deleted anyhow. For such system an interface is required to which the user can select one or multiple jobs to be retried and one or multiple jobs to be deleted. For UX reasons I cannot let the user process the buried jobs one by one. -- Jurian Sluiman -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
