On Aug 25, 10:04 pm, Keith Rarick <[email protected]> wrote: > You're looking at an outdated copy of the protocol doc. > > https://github.com/kr/beanstalkd/blob/v1.4.6/doc/protocol.txt#L247-L248 > "A client can delete jobs that it has reserved, ready jobs, > and jobs that are buried." > > Since a job becomes ready when it times out, deleting a > formerly reserved job will succeed.
Ah, I got to the protocol page from the FAQ page, which I guess needs to be updated :P https://github.com/kr/beanstalkd/wiki/faq http://github.com/kr/beanstalkd/tree/v1.1/doc/protocol.txt?raw=true > > ... that way my > > worker would know it no longer "owned" the job. > > It still wouldn't find this out until after it had finished processing > the job and was ready to delete it, at which point it's too late to > do anything useful with the knowledge. The ability to delete > ready jobs seems more useful, so we added the feature. Right, but in that case I as planning on having my "manager" be ready to see that job ID again and in that case, don't process it, just delete it directly. But anyway, since what I'm doing is related to stuff that cannot be undone, I decided to delete the jobs as soon as the "manager" gives it to the "worker". Thanks for the clarification. -- 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.
