Thanks but it seems that in this example (if I have understood correctly) it loads the entire request into memory. I need to convert stuff on the fly using streams on both input and output as both may be huge. I have a number of stages of transformation and it wouldn't take very many requests to bring the machine to a grinding halt if everything is being done in memory at each stage.
I have decided to do it in java with jetty, servlets and embedding jython (which bizarrely for large datasets seems to be more efficient, standard c python perfomance plunges after certain in memory data sizes - I believe its the GC strategy not scaling well from what I have heard). On 25 Aug, 21:41, Peter Bengtsson <[email protected]> wrote: > Here's an example:http://www.djangosnippets.org/snippets/1322/ > > On Aug 25, 5:43 pm, John <[email protected]> wrote: > > > > Isn't it just > > > request.raw_post_data > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
