Especialy for large files: http://grid.net.ru/nginx/upload.en.html
large file-> nginx -> files_on_local_fs -> headers_with_path_to_your_app 07.08.2009, в 0:32, tom написал(а): > > Hello, > > I run a site where people upload large files, up to 300MB, currently > about 200 times a day. The upload works with a perl script, where the > other parts of the site are done in php. > > Now, we want to move the whole site to python, and werkzeug seems like > a good choice. But what is the best way to take care of the uploads? > One of the options is [1], although the whole application needs to be > wrapped, which makes modularizing difficult. > Another option is passing the whole file to a werkzeug function in a > FileStorage wrapper, but this is not transparent, in that I would like > some control about things like the temporary file/folder, and some > kind of progress bar. I also found the "not so clever" uploader on > trac. > Alternatively, we could rewrite the perl script in python (or even > leave it like it is) and have a separate wsgi application running. > > What are your experiences of file uploads? Are there general > objections against using python/werkzeug/wsgi for large uploads, and > then how would I best do it? > > Regards, > Tom > > > [1] http://www.gawel.org/docs/gp.fileupload/ > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pocoo-libs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pocoo-libs?hl=en -~----------~----~----~----~------~----~------~--~---
