Sounds like something better suited to more persistent storage, such as a DB table. You could even cache the table if load is an issue, and trash/remake the cache entry whenever you modify the task list.
On Wed, Feb 24, 2010 at 11:19 AM, Martin Sarsale <[email protected] > wrote: > Guys: > > We're using beanstalkd to maintain a list of tasks that need to be > executed in order "forever". > > We're currently: > 1) reserving the job > 2) processing it > 3) deleting it from the queue > 4) adding it again, at the end > > Can you think a better way to do this? Maybe we're forcing beanstalkd > to do something it's not designed for? > > Tnx > > > -- > Martin Sarsale > msn: [email protected] > jabber: [email protected] > twitter: http://twitter.com/runixo > linkedin: http://www.linkedin.com/in/msarsale > sumavisos: http://www.sumavisos.com > blog: http://runa.tumblr.com > > -- > 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]<beanstalk-talk%[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.
