Thanks Michael On Aug 21, 2015 5:58 AM, "Michael Barrow" <[email protected]> wrote:
> When you put a job into a tube, and a worker reserves it, it is the only > worker that will ever see that job. There are a few exceptions, including: > 1. if it fails to remove it from the tube prior to the timeout set for the > job, beanstalkd will make the job available to another worker. > 2. if the worker buries the job, it will remain in the tube, but in a > buried state where it won't be available to be reserved without being > kicked. > > Implementing pub/sub using beanstalkd is possible, but will require a > substantial amount of work in your codebase to implement the functionality. > > On Mon, Aug 17, 2015 at 9:16 AM, Suman patro <[email protected]> wrote: > >> Thank you so much. >> But your 1st and 2nd answers conflict. >> If copies can be given to multiple Consumers(1), then why a copy can be >> consumed by a single consumer (2)..if u can please elaborate. >> Sent from my Sony Xperia™ smartphone >> >> >> ---- Jens Rantil wrote ---- >> >> Hi, >> >> Den söndag 16 augusti 2015 kl. 08:39:37 UTC+2 skrev Suman Patro: >>> >>> 1. Is publish-subscribe model supported in beanstalkd? >>> >> >> Not explicitly, however you could always have a producer put multiple >> copies to different tubes if it knows who the consumers are. Do note, >> however, that this might be considered a hack. >> >> >>> 2. Can job queues be used as message queues and vice versa?.. State some >>> of the few. >>> >> >> Define message queue. You could always send messages but each task will >> only be consumed by one worker. >> >> >>> 3. Can Beanstalkd be used as a message queue?? >> >> >> If "message queue" is what I described in 2), then yes. >> >> Cheers, >> Jens >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "beanstalk-talk" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beanstalk-talk/y6rvlenH7P8/unsubscribe. >> To unsubscribe from this group and all its topics, 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. >> > > > > -- > michael at barrow dot me > +1.541.600.2027 > > "Do not anticipate trouble, or > worry about what may never happen. > Keep in the sunlight." -- B. Franklin > > -- > You received this message because you are subscribed to a topic in the > Google Groups "beanstalk-talk" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beanstalk-talk/y6rvlenH7P8/unsubscribe. > To unsubscribe from this group and all its topics, 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.
