title: How should I use Celery when task results are large?
body: <p>What's the best way to handle tasks executed in Celery where the result is large? I'm thinking of things like table dumps and the like, where I might be returning data in the hundreds of megabytes.</p>
  
  <p>I'm thinking that the naive approach of cramming the message into the result database is not going to serve me here, much less if I use AMQP for my result backend. However, I have some of these where latency is an issue; depending on the particular instance of the export, sometimes I have to block until it returns and directly emit the export data from the task client (an HTTP request came in for the export content, it doesn't exist, but <em>must</em> be provided in the response to that request ... no matter how long that takes)</p>
  
  <p>So, what's the best way to write tasks for this?</p>