The short answer to your questions is: no The long answer is still no, but you can probably *force* things to do what you’re saying with some more logic existing outside of the message queue itself.
Might be easier / more robust to have 1 tube and 1 job and then your consumer does what’s needed. Many modern languages allow you to run multiple threads in parallel. -- Chad Kouse Sent with Airmail On July 15, 2014 at 3:12:00 PM, Wickman ([email protected]) wrote: Hi In my case, jobs must pass through several steps before they are done. Some steps can be done in parallell. I figured I solve this by moving jobs between tubes, say I use tubes like "step1" which then moves the job to tubes "step2" and "step3" etc. Is this a sane approach? I see a few issues with this approach: Is there any way of moving a job from one tube to another safely/atomically (put + delete)? Copying the same job to several tubes for parallell processing doubles the amount of RAM needed. Is there any way around this? Just asking for some ideas and "best practices" here. Thanks! -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk. For more options, visit https://groups.google.com/d/optout.
