Add ability to change [FileMode] of the download by introducing [Dio…
…FileMode]
New Pull Request Checklist
- [Yes] I have read the Documentation
- [Yes] I have searched for a similar pull request in the project and found none
- [Yes] I have updated this branch with the latest
mainbranch to avoid conflicts (via merge from master or rebase) - [Yes] I have added the required tests to prove the fix/feature I'm adding
- [Yes] I have updated the documentation (if necessary)
- [Yes] I have run the tests without failures
- [No] I have updated the
CHANGELOG.mdin the corresponding package
Additional context and info (if any)
Add the ability to change the [FileMode] of the download without altering the default value, which is [FileMode.write], to make resuming downloads easier to implement by introducing [DioFileMode] and mapping it to FileMode in [DioForNative] without breaking web_adapter
Can you please explain how this change enables resuming downloads? Please also add tests for both cases, so it will not get broken in the future.
Can you please explain how this change enables resuming downloads? Please also add tests for both cases, so it will not get broken in the future.
When downloading a file a stream is opened and a Random Access File are opened in the client side to store bytes the current implementation to open a Random Access File is [FileMode.write] this mode creates a new file and overwrite the existing one if it already exists
changing the file access mode to [FileMode.append] or [FileMode.writeOnlyAppend] with change the behavior to write to the end of the file
So if you had already started downloading a file and for some reason the download stopped let's say a network problem and you set [deleteOnError = false], the file had already downloaded 50% and it's not deleted it exists but is not complete
You check if the file exists and get it's size then you request to download the file again by requesting a partial content setting the range header to file size, that means skip downloading the 50% you already downloaded then you append the remaining 50% to the end of the file and here it's you resumed your download with minimum ease.
Can you please explain how this change enables resuming downloads? Please also add tests for both cases, so it will not get broken in the future.
Ok, I will add tests.
I wonder whether it makes sense to automatically add range header in the case of a resuming download, that way it would work out of the box, without the user needing to implement anything. The server needs to support them though. (This is not something which necessarily needs to be added to this PR though, I guess)
I wonder whether it makes sense to automatically add range header in the case of a resuming download, that way it would work out of the box, without the user needing to implement anything. The server needs to support them though. (This is not something which necessarily needs to be added to this PR though, I guess)
Yes, it's a good idea. I think it's rare to find a server that doesn't support range requests. Should I change the implementation to just a boolean parameter in [Dio.download] called resume ? If the server doesn't support range requests don't use it
I wonder whether it makes sense to automatically add range header in the case of a resuming download, that way it would work out of the box, without the user needing to implement anything. The server needs to support them though. (This is not something which necessarily needs to be added to this PR though, I guess)
I added test case for the file mode append, now can you review the code again
@ueman Could you follow above reviews and stamp this if applicable?
The CI is complaining about the v1 of dio_web_adapter, which should be updated after the PR has landed (I'll do that).
I'll merge this once I have cleared my recent works to gain some bandwidth.
@AlexV525 Workflow needs approval
@AlexV525 What is the next step is there is a problem or you will merge it when possible ?
I'll merge this once I have cleared my recent works to gain some bandwidth.
↑
Excellent work. Hope release as soon as possible.
Given the fact that the check failed with the v1 adapter, the change is a breaking change that does not consent to the top description. So I updated the top comment according to the latest result.