I have seen various posts where developers have opted for the chunking option to upload files, particularly large files.

It seems that if one uses the chunking option, the files are uploaded and progressively saved to disk, is this correct? if so it seems there needs to be a secondary operation to process the files.

If the config is set to allow large files, should plupload work without chunking up to the allowed file size for multiple files?

有帮助吗?

解决方案

It seems that if one uses the chunking option, the files are uploaded and progressively saved to disk, is this correct ?

If you mean "automatically saved to disk", as far as I know, it is not correct. Your MVC controller will have to handle as many requests as there are chunks, concatenate each chunk in a temp file, then rename the file after handling the last chunk. It is handled this way in the upload.php example of plupload

if so it seems there needs to be a secondary operation to process the files.

I'm not sure I understand this (perhaps you weren't meaning "automatically saved to disk")

If the config is set to allow large files, should plupload work without chunking up to the allowed file size for multiple files ?

The answer is yes... and no.... It should work, then fail with some combination of browsers / plupload runtimes when size comes around 100 MB. People also seem to encounter problems to setup the config.

I handle small files (~15MB) and do not have to use chunking. I would say that if you are to handle large files, chunking is the way to go.

许可以下: CC-BY-SA归因
不隶属于 StackOverflow
scroll top