On Tue, Apr 15, 2014 at 1:42 AM, Adrian Holovaty <adr...@holovaty.com> wrote: > On Sun, Apr 13, 2014 at 11:30 PM, <m...@pdx.edu> wrote: >> >> Is the Django community interested in supporting HTTP range requests in >> django.views.static.serve? > > > I definitely support this. > > I've gotten bitten several times by the development server not supporting > Range headers, and it's the kind of a problem that is quite hard to debug. I > recall it took me about an hour to determine why audio wasn't seeking > properly when it was being served by the development server. > > To Russ' point about not using the server in production: we can support > Range without sacrificing our "don't use this in production" goal. Let's > treat our users like consenting adults. We should definitely discourage > people from using the development server in production, but not to the point > where we're neutering the server, making development more difficult.
I accept the use case, but I'm still not wild about the solution. I can certainly accept that making it easier to develop media-rich apps would be a good thing. However, rather than add a bunch of features to a view in Django and then try to describe when you shouldn't use it, I'd prefer to use that effort to replace the devserver with something equally easy to use, but based off a base that is an actual real live web server. That way, we'd end up with a "devserver", but it would be an actual server, not a hack with a bunch of "please don't actually use this" warnings, we don't end up spending a bunch of time developing a feature that is already implemented better elsewhere, and it would be one step closer to having production mirror development. This is a lot more plausible now that we have good packaging tools. There have also been a bunch of vague discussions over the last couple of years on this topic. That said, I'm also not especially motivated to work on this personally - I'm just expressing my architectural concerns. Count me as a -0, not a -1. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq849XH78rGyYBiWxLADGusJxd_rB%2BQRyXizD4neozkLj4tg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
