This repository was archived by the owner on Nov 19, 2018. It is now read-only.
Issue with Concurrent Chunking #66
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In case of concurrent chunking, first all chunks are stored into a folder,
then a write operation is performed and finally I success request is sent
back. In async mode, this write operation and sending request to server is
not in sync. Therefore, many a times, you will havea request sent to the
server with an incomplete file (chunks not properly combined).
FineUploader after sending all the chunks and getting a stored success request,
can send a post request to another route "/uploads/chunksdone" to know whether
the process is complete. This feature can be used to solve the problem explained
in the above paragraph.