News for hackers. Stuff that matters.
Re:Rails 4 will establish a new background job queueing API by simonw on Friday April 27, 2012 @12:58PM (#3899980)
Yes, that's exactly what I meant. Like you say: today, a background queue should be part of the default stack for a web (just like a template engine, database, session storage and a cache have been in the past - components which Django has provided since day one). No need to re-implement celery, but encouraging the Django ecosystem to embrace offline queues (and letting reusable apps know that they can push tasks in to an abstract queue of some sort) would be very healthy.
Re:Rails 4 will establish a new background job queueing API by megaman821 on Friday April 27, 2012 @01:09PM (#3900033)
I agree that this would be a great addition to Django. Celery may not fit everyone's needs. I would rather have something lighter weight for dev.