Just curious, why is it better to put all jobs through a single tube? -- Chad Kouse
On Wednesday, December 5, 2012 at 7:59 PM, Keith Rarick wrote: > On Wed, Dec 5, 2012 at 4:01 AM, Jason Judge <[email protected] > (mailto:[email protected])> wrote: > > I'm assuming a separate pipe for each type of task will be useful > > > All else being equal, it's better to put all jobs through a single tube. > Each job should be a complete description of the work to be done, > so that a worker can pick it up and run it without, for example, > knowing which tube it came from. > > If you have two workers with different capabilities (say, they're > written in different programming languages with different codebases > and process disjoint subsets of jobs), that would be a good reason > to have a tube for each type of worker. > > -- > 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] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/beanstalk-talk?hl=en. > > -- 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.
