Skip to content
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

window.requestFileSystem #2

Open
MariasStory opened this issue Nov 21, 2020 · 2 comments
Open

window.requestFileSystem #2

MariasStory opened this issue Nov 21, 2020 · 2 comments

Comments

@MariasStory
Copy link

Hi @subins2000, it seems to be thought through solution, thanks for open sourcing ;-)
Please implement direct file write with window.requestFileSystem an the possibility to continue partially downloaded file.

Let's say, peer1 send a file to peer2 and the connection is broken.
After some time, the peer1 is sending the same file to peer2. The peer2 is pointing to the partially downloaded file and the download continues where is broke.

@subins2000
Copy link
Owner

I see that winfow.requestFileSystem is a Chromium thingy. Implementing that is not a priority since the main intention of this library is cross-platform/browser file share.

As for file resuming, if the connection close in between and sender uploads the file again with the same file ID, then the transfer will be continued on the receiver side.

@MariasStory
Copy link
Author

Hi, thanks for the answer.
I just tried with the webdrop and indeed the file transfer is resumed. However, at least in Chromium, it gets somewhat messy with the parts of the files, that need to be combined.

You can close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants