Yes, you are perfectly right about the fact that this is a bad implementation. the fact is that where i host the code it does not support celery (so far). so i've to find out a workaround to be able to process a bunch of external APIs Call (that include the one for sending email). we'll probably keep the javascript reloading to process junks, waiting for the support of celery.
BTW: the StreamingHttpResposnse, when should it be used? i get the example on the docs about writing a cvs, pdf or similar, but, what else? Thanks for the help. On Wednesday, February 27, 2013 6:23:52 PM UTC+1, Stefano Tranquillini wrote: > > Django 1.5 is just came out and it ships the StreamingHttpResponse. > > What i want to do is to print the output of a stream response into a > template, having for example a bar that grows based on the streamed data > (something similar to a loading bar). > > so far i've found a solution that basically is to write the pieces of the > final html page into the generator function, so each yield does a > render_to_text of a piece of the final html page (i splitted it manually) > putting each time the data just processed. > > The problem of this solution is that i can't have the loading bar. What > I'm able to have are incremental data, so i can print out the list of > processed data, but it's different to what i want to do. > > Is there a way to do what i would like to do? > > thanks. > > > -- You received this message because you are subscribed to the Google Groups "Django users" 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 http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
