Closed ryanjohns closed 11 years ago
As I mentioned in #21, I am freezing work to make backburner out of the box IronMQ compatible. Too hacky and too much workaround code. I want to focus on making backburner the best beanstalkd client first and foremost and may revisit this someday as a plugin. Hope everyone understands.
Thanks for taking the time to investigate it @ryanjohns, it helped me understand the challenges to getting this working in backburner core.
This fixes IronMQ auth and prevents using the
stats-job
command as it is not supported by IronMQ. There is still an issue with the worker because IronMQ will only wait for 60 seconds for a message to become available before returning a nil response instead of waiting indefinitely like beanstalkd. The nil response breaks processing in beaneater so I'm not sure how to deal with this.