FWIW, I vaguely recall how the last thread on X-sendfile and the files API
got conflated (derailed?) and as far as I understood it then and as far as I
understand it now, they're related only because some backends (which we
currently don't directly support) are difficult to work with without such
conflation. That doesn't mean we can't solve one problem at a time, however.
Especially when one problem *is* simple, and the other is not.
They're both good goals, and problems worth solving, but IMHO there's no
reason that they couldn't be two separate features.
+1 on a simple solution for X-sendfile, +0 on making the file API more
compatible with a broader range of backends, -1 for solving both issues
together.
- Gabriel
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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.
