On Sunday, October 28, 2012 11:24:53 PM UTC+1, Jurian Sluiman wrote: > > The only method I can come up with now is to delete the job being worked > on, create a clone of the job, add the new data, put that in the queue > again and bury it directly. This seems a bit odd with a lot of steps. Is > there anything I miss in this picture? The same question applies to > releasing jobs during the work cycle, since I can't imagine something > different here too. >
Now I have looked more closely to the protocol ( https://github.com/kr/beanstalkd/blob/master/doc/protocol.md) I notice there's a flaw in above outline. You can only bury a job when you have it reserved. I know the bury command is "bury <job id> <priority>" but according to the manual you get a NOT_FOUND when you haven't reserved the job if you try to bury it. The release is still possible with additional data, I will delete the job and put a new clone into the queue (not favourable, but doable). The bury command is quite important to me (one big advantage of beanstalk to other queues). How is "user inspection" possible with a bury when I cannot inform the user why the job was buried? Usually you want to catch an exception and log the exception type and message. I have no experience in C coding. If this is a missing feature I really hope there is a contributor to help on this. If it is not possible at all, please let me know. I can look for an expert to do it for me, so I can use these features. The license is MIT I just checked, so that shouldn't be a problem. --- Jurian Sluiman -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/beanstalk-talk/-/C5to9zYr4OUJ. 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.
