On Tue, Jun 22, 2010 at 9:00 AM, Gert Van Gool <gertvang...@gmail.com> wrote: > What's wrong with the current StorageBackends? > Apart from the fact that everything goes through Django first, which imho > isn't a bad default solution (easier for parsing and the like...).
Just to clarify: django-filetransfers is an addition to the storage backends. IOW, you use both in combination. The storage backends API has these problems: 1) It doesn't work with all storage solutions (e.g., App Engine Blobstore) 2) Pushing large files through Django actually is really bad and depending on your configuration it can block a whole Django instance for the duration of the upload (small files might be fine, but still this eats resources unnecessarily). Even if you use multi-threading with Django it'll block a thread for a long time, so if you have lots of uploads going on your whole web server can become unresponsive. Bye, Waldemar Kornewald -- 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.
