Use celery's backends

[jonashaag]

You could re-use celery (https://github.com/ask/celery) backends instead of rolling out your own

[fish2000]

Thanks for the tip -- I am aiming for something more lightweight than celery with django-signalqueue. But a celery backend adaptor is in the works, for those who have it set up already; I'll put up that code in a separate branch if you are interested in using it.

[eamonnfaherty]

is there any word on that branch? I am already using celery and would rather not have two similar backends.

[fish2000]

@eamonnfaherty sorry to address this only now -- I've been divided in my attentions, but who isn't these days -- but I should be pushing a working draft of the Celery backend layer stuff this week.

I looked at the old source and then tossed it; starting over now that I'm more familiar with Celery's ethos is going to be awesome: a lot of what Celery provides out-of-the-box works harmoniously with Django signal paradigm... meaning that ultimately django-signalqueue will require almost no configuration for those who are already Celery-ing.

(This is because it's serendipitously trivial to override the queue backend's low-level enqueue()/retrieve()/dequeue() API, which would be a ton of architectural circuitousness in, like, most other cases. My previous mistake was trying to write the Celery interface like the other backends; if this works out as I think it will I'll be able to easily support other robust queueing interfaces e.g. ØMQ.)

Anyway that's the state of things, in a nutshell.

[eamonnfaherty]

Great, I ended up rolling my own solution but I seriously doubt it will be as elegant as what you are suggesting.

I am eagerly awaiting an update!

btw, do not worry about the delay - you are providing valuable code for free!