So a channel must result in a response to a browser? It seems both from the config (routing things into functions, or queues) and the underlying tech (using redis or whatever) sounds very similar to celery.
>From the docs: - Interface servers, which communicate between Django and the outside world. This includes a WSGI adapter as well as a separate WebSocket server - we’ll cover this later. - The channel backend, which is a combination of pluggable Python code and a datastore (a database, or Redis) and responsible for transporting messages. - The workers, that listen on all relevant channels and run consumer code when a message is ready. I get that the goal of this is for asynchronous web requests, but if it's generalized right it seems like it could cover doing any kind of work without the pressure of completing a web transaction in a timely fashion. -Ben On Tue, Dec 15, 2015 at 2:09 PM, Aymeric Augustin < [email protected]> wrote: > Hi Ben, > > Celery and channels don’t tackle the same problem. > > Celery is an asynchronous task queue. It is designed perform expensive > work after responding to a HTTP request. At that point there is no possible > communication with the browser. > > Channels is an asynchronous message framework. It enables asynchronous > messaging between the browser and Django, going beyond the current > request-response structure. > > Best regards, > > -- > Aymeric. > > > > On 15 déc. 2015, at 22:35, [email protected] wrote: > > Hey, > > Channels sounds a lot like celery (or celery sounds like part of > channels). Is that a fair read? Looking for tighter REST integration > either way. > > Thanks, > -Ben > > On Friday, December 11, 2015 at 10:19:00 AM UTC-8, Andrew Godwin wrote: >> >> Hi everyone, >> >> For those who haven't seen, Mozilla has awarded $150,000 to Django for >> work on Channels and request/response improvements lifted from REST >> Framework. More in the blog post here: >> https://www.djangoproject.com/weblog/2015/dec/11/django-awarded-moss-grant/ >> >> I'll be coordinating this effort for the most part, but we're still >> working out who to fund and the roadmap for the project, as well as work >> out how we can pay people for their work on a different scale to the Django >> Fellowship, so it might take a bit of time! >> >> I'll be back on here with some questions for people to discuss/answer >> about the channels design at some point soon, but a lot of the basic design >> is already up at http://channels.readthedocs.org, so take a read over >> that if you're interested. >> >> What I can say is that my intention is to both bake Channels into the >> next major release of Django, as well as hopefully release a pluggable app >> version that will run on 1.8 and 1.9 - I have some plans around how to do >> that effectively, but they involve hitherto unforged paths around Django >> and how we package dependencies, so I can't say we'll get there 100%. >> >> Andrew >> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/299ede52-6ae4-46d3-8667-40e7fa6a89a6%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/299ede52-6ae4-46d3-8667-40e7fa6a89a6%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-developers/3pTMfHa8SFE/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/D5557CBB-03D8-4DB2-AAFA-B4063E227D8A%40polytechnique.org > <https://groups.google.com/d/msgid/django-developers/D5557CBB-03D8-4DB2-AAFA-B4063E227D8A%40polytechnique.org?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- *Ben Liyanage *|* Software Engineer *|* Rentlytics, Inc.* Phone: (410) 336-2464 | Email: [email protected] 1132 Howard Street, San Francisco CA 94107 Visit our Website <http://www.rentlytics.com> | Watch our Video <http://youtu.be/Pe_9KE_fj34> -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CADgLBUOdzxx1LxprsggcYKH22SctV%3DQsqLVsr-yJCspQ11gEbg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
