support customized result backend about machinery HOT 4 CLOSED

This was related to another issue: #27

I chose to make result backend mandatory for now as otherwise it was easy to get errors and the documentation was a bit misleading so I fixed that too. Perhaps I should revisit that decision.

I will be travelling this weekend so I might not be able to look at this until next week.

EDIT: Basically, most features (sending a task and waiting for a result), chords, groups etc do not work without a result backend.

from machinery.

@balzaczyy Is your backend too customised? Ot do you think it is generic enough you could contribute it via a pull request? If it's not too specific to your use case, it can be added as another backend option.

from machinery.

@balzaczyy git pull

It should allow custom backends again. Sorry.

from machinery.

Cool. Thanks. I'm using ElasticSearch as the result backend. But it's only partially implemented for my own purpose. I will try create a pull request when I finish the remaining function.

from machinery.