> But I have concerns about performance in the common case. File upload is inherently a slow process strictly limited by the connection speed so it is not clear that any kind of performace problems would be noticable at all (even if there were such problems)
Loading files into memory is *extremely* limiting, there are great many applications, photo or music albums or rich web applications that need file upload. The last thing one wants is to have to worry about balooning up the memory footprint because of something as trivial as uploading a file. No sane application slurps up files of unkown size, why would a generic web framework do so? > rare to allow multi-tens-of-megabytes uploads from Joe Public The question rather is why make Django *incapable* of dealing with files without worrying of what a user might choose to upload? When the solution is rather trivial? And by the way, thanks for the nice patch Ivan. I'm (re)writing an application to Django and would have never done so had there not be this hope that this issue will be settled properly. Istvan --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
