The solution implemented in 2.5 works with 3 parameters:
<PARAM NAME="resume" VALUE="true">
<PARAM NAME="chunksize" VALUE="5000000">
<PARAM NAME="chunkmode" VALUE="onflyrange">
"onflyrange"allows to include "Content-Range" header in each multipart HTTP POST request with range of bytes uploaded. Server-side script appends chunks in the final file. To make resume work, the applet send an HEAD request (as usual) to get remote file size (or CRC/MD5) and then know at which offset to restart upload.
This solution avoids modification in our sample scripts (which already take "Content-Range" header into account) and also avoids the final file recomposition (so overall upload is faster).
Feature request (resume + chunks)
Re: Feature request (resume + chunks)Hello
That is great Any news of that feature ? Corto Re: Feature request (resume + chunks)Yes, this is implemented in 2.5. We have an issue with "authentication" parameter and we're going to fix it for 2.5 final.
Re: Feature request (resume + chunks)By the way, i'am still testing and when you interrupt an upload, all the chunks parts already uploaded are not deleted ...
Re: Feature request (resume + chunks)When will the 2.5 will be released ?
Re: Feature request (resume + chunks)At the beginning of October. If you purchase the current version then we could provide you the testing 2.5 before official release.
Re: Feature request (resume + chunks)This feature is working great so far, but it will be really useful for the user if the progress bar will change based on what chunk is currently uploading.
If you upload 50% of a file and for some reason you were interrupted, dragging the file again it will show the progress bar from beginning (and not from 50%), making the user think he has to reupload everything. |