Message from discussion
Is CELERY_RESULT_BACKEND necessary?
Date: Mon, 27 Aug 2012 14:26:54 -0700 (PDT)
From: Kevin O'Connor <kevin.ocon...@arc90.com>
To: celery-users@googlegroups.com
Message-Id: <3c65238e-cb8d-498b-8f52-82e8635b1ede@googlegroups.com>
Subject: Is CELERY_RESULT_BACKEND necessary?
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_764_12126625.1346102814815"
------=_Part_764_12126625.1346102814815
Content-Type: multipart/alternative;
boundary="----=_Part_765_2571754.1346102814815"
------=_Part_765_2571754.1346102814815
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
I see it defaults to nothing, so does that mean it's not necessary for
normal operation? Is it only for debugging/monitoring purposes?
------=_Part_765_2571754.1346102814815
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
I see it defaults to nothing, so does that mean it's not necessary for normal operation? Is it only for debugging/monitoring purposes?
------=_Part_765_2571754.1346102814815--
------=_Part_764_12126625.1346102814815--