On Wed, Sep 4, 2013 at 2:36 PM, Javier Guerra Giraldez
wrote:
> above that, Redis is a clean, fast and very scalable platform for
> queues. if you don't have heavy buzzword dependency, i wouldn't
> bother checking AMQP systems and stay with Redis.
>
A thousand times this. You don't need AMQP sys
On Wed, Sep 4, 2013 at 12:28 PM, wrote:
> What were people using back in PHP days, cron all the way?
MQs have existed for a long time; but weren't so popular. I think the
Twitter problems were the wake-up call for most people.
in part because ghetto queues do work, and work well up to a point
On 3 september 2013 15:25:42 UTC+2 Russell Keith-Magee wrote:
>
>
> On Tue, Sep 3, 2013 at 9:50 PM, > wrote:
>
>> In my Django application I need to schedule some tasks to run in future.
>> Celery is not an option here because some crucial options - mainly, the
>> ability to revoke() a task - are
On Tue, Sep 3, 2013 at 9:28 AM, Dig wrote:
> My django application is host in uwsgi, which is support timer(interval). So
> I insert my task parameters into database and execute tasks in timer
> handler.
note that uwsgi also has a spooler facility...
--
Javier
--
You received this message be
I have a similar need. And I implement this feature with uwsgi.
My django application is host in uwsgi, which is support timer(interval).
So I insert my task parameters into database and execute tasks in timer
handler.
Regards,
Dig
On Sep 3, 2013 9:26 PM, "Russell Keith-Magee"
wrote:
>
> On Tue
On Tue, Sep 3, 2013 at 9:50 PM, wrote:
> In my Django application I need to schedule some tasks to run in future.
> Celery is not an option here because some crucial options - mainly, the
> ability to revoke() a task - are only available with fully-featured MQ
> backend and I only have a limited
6 matches
Mail list logo
