On December 16, 2015 6:01:58 PM GMT+10:30, Shai Berger <[email protected]> wrote: >On Wednesday 16 December 2015 08:08:59 Markus Holtermann wrote: >> From my point of view the major non-functional difference is the >> interaction with a client in *some way*. While a celery task runs >without >> any form of client, a channels method would mostly do that. Picture >the >> following example: >> >> A user uploads an image. This could happen through the common >> request-response cycle. When the upload is done the server creates a >> celery task to generate a bunch of thumbnails and returns a http >response. > >But here is Ben's point: Why would you introduce an additional moving >part >here (Celery), when the Channels documentation specifically mentions >this as a >use-case?
Because my "generate a thumbnail" might me some video decoding or another long running process that would block possible further requests, or simply because I could easier reuse that particular task in other parts of the website as well. >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". /Markus -- 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/D484E906-05BC-4959-A786-9F80BFF41B5C%40markusholtermann.eu. For more options, visit https://groups.google.com/d/optout.
