Hi, A few questions about your situation:
Does order matter amongst the observers? Are all the observers potential consumers? How is the decision made about consuming (e.g. can there be 2 possible consumers and how do you pick?) Can your situation be better handled by an MQ like RabbitMQ for the broadcast and a job queue (beanstalkd) for the "only one consumer" aspect? Regards, Erich On Apr 29, 3:58 pm, DeRailed <[email protected]> wrote: > Hi, > > First of all thanks for this great project ! > > I have a queue with a series of observers that just look at jobs as > they come by and release then right > away and a single consumer that will actually delete the job from > the queue. > > I would like to implement a strategy where all "observers" get a > crack at looking at the job before it is > actually consumed by the single consumer. Hence having the single > consumer give all other workers a > chance to look at the job before it actually consumes it. > > Is this feasible with beanstalkd ? If so how ? I am currently using > the ruby beanstalk-client to interface with > the queue. > > Thanks !! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
