On Tue, Nov 2, 2010 at 4:19 AM, Ivan Sagalaev <man...@softwaremaniacs.org> wrote: > On 11/01/2010 11:21 AM, Mark wrote: >> >> Ticket #14594 >> <http://code.djangoproject.com/ticket/14594> > > From a quick look it can be fixed in two ways: > > - HttpRequest.raw_post_data can always explicitly ask for content_length > bytes. If content_length is absent just treat it as 0. > > - WSGIRequest can wrap all wsgi.input into a LimitedStream (now it's done > only for known fragile sockets). > > I don't like pure Python wrappers moving bytes in performance critical > places, so I'd go with the first approach. Does anyone foresee any bad > things with it?
The former looks like the right approach to me -- in fact, it looks to be a pretty close rendition of what the code used to do. I've made the change in r14435. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
