Re: render_GET and memory consumption

On 22 Dec, 06:51 am, [email protected] wrote:
>
>On Dec 21, 2010, at 2:24 PM, [email protected] wrote:
>>Instead, you have to go all the way to producers/consumers, and only 
>>write more data to the transport buffer when it has finished dealing 
>>with what you previously gave it.
>
>While everybody should of course use producers and consumers, I feel 
>like there should be a twisted core ticket for this behavior of 
>transport buffering, and a twisted web ticket for this behavior of the 
>request buffering.  The naive implementation _could_ be much cheaper 
>memory-wise; at the very least, twisted.web.static.Data ought to do the 
>smart thing.

Fixing Data sounds like a good idea.  I don't know what improvement to 
the transport buffering you're thinking of, though.  It doesn't seem 
like there is an obvious, generally correct fix.

Jean-Paul