On Fri, Sep 17, 2010 at 1:37 PM, <span dir="ltr"><<a href="mailto:chris.dent@gmail.com">chris.dent@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, 17 Sep 2010, Ionel Maries Cristian wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I feel this spec puts too much burden on applications - having to process<br>
all those byte strings and even having to add Content-Length even for naive<br>
buffered-body apps.<br>
</blockquote>
<br></div>
The Content-Length requirement is a big killer for me. I'm usually<br>
generating content in apps, rather deep in a stack of middleware-like<br>
pieces that may or may not be looking at or modifying that content.<br>
I don't want to a) have to unwind my generators at each level b)<br>
reset the content-length here there and everywhere.<br>
<br>
It could be I'm doing it completely wrong, but it works rather<br>
nicely.<br></blockquote><div><br>I'm unclear what exactly you guys are reacting to. This?<br><br><ul class="simple"><li>The server must not inject an additional <tt class="docutils literal"><span class="pre">Content-Length</span></tt> header
by guessing the length from the response iterable. This must be set
by the application itself in all situations.</li></ul><br>I'm also not sure what motivated this particular change, but I don't have any opinion one way or the other.<br><br></div></div>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>