-
-
Notifications
You must be signed in to change notification settings - Fork 686
pause/resume upload #393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hm. Not very familiar with the code currently, but it sounds me like it is some kind related to #371. So let the issues be linked, so we can think for them as one. Because both will be some workaround in the progress handler. |
For resuming to be able to occur, the server needs to stream the request to a persistence layer. Upon attempting to resume, the client must ask the server about what it has already received and then only send the rest. This can be achieved with the HTML5 File API (IE. Blob#slice). I have personally used Resumable.js to achieve this functionally. However, this is something you have to create on top of Formidable. It has nothing to do with parsing multipart requests. Thus, I am closing the issue. You can still comment and I will attempt to answer to the best of my ability. |
Uh oh!
There was an error while loading. Please reload this page.
Is it possible to resume upload in the next request if the current request failed/calceled by the client?
If user tries to upload 10Gb file and then in the middle of the process - closes his laptop. What is the better way to save the first part of the file and resume upload to the same file in the next request?
The text was updated successfully, but these errors were encountered: