On Wed, Dec 16, 2015 at 9:52 AM, Markus Holtermann <[email protected] > wrote:
> > >If I get it right -- Curtis' description is spot-on; some tasks will > >still > >need Celery, Channels will take care of many others. > > For me it's more a question of "is a client directly involved". > I don't agree; I think it's more "do you have enough workers to handle this". Channels makes all workers serve all requests, so if you're doing e.g. video encoding you can't segregate it from request handling. However, you could have multiple channel backends and thus multiple worker pools to achieve this. 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/CAFwN1uo58xzT_yt5PoZ47RMu-S3biXjVLggned-_TS4R_ba80g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
