Track tasks and feature requests
Join 40 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesWhen seeding a file/folder from disk, don't perform extra copy to /tmp #357
Comments
This comment has been minimized.
This comment has been minimized.
|
I'm sure feross can enlighten us, but I'll take a stab at the question. From my limited work with the file api, it's not easy to access data from the outside of the web sandbox (by that I mean not possible). So the options would be too keep the data in memory (hope you have a lot!) or write it to disk somewhere you can access. |
This comment has been minimized.
This comment has been minimized.
|
Oh sorry, I forgot an important thing. It's with webtorrent in a node server (webtorrent-hybrid). Of course in a browser I agree there is no many options. |
This comment has been minimized.
This comment has been minimized.
|
@Chocobozzz You're right, copying to /tmp is not really needed if you're seeding a file that you already have on disk. This is a bug! PR welcome! |
closes webtorrent#357
This comment has been minimized.
This comment has been minimized.
|
Released as 0.50.1, thanks to a PR from @janza |
This comment has been minimized.
This comment has been minimized.
|
Thanks guys ! |
Hi !
If I want to seed a file from (just an example) /home/me/videos/awesome.webm I see that webtorrent copy it as /tmp/webtorrent/xxx/xxx.webm. I wanted to know if this was really needed, since the file is already on the disk.
This could be annoying with big videos (1Go), disk space would rapidly decrease and the seeding would take much time since the disk should copy 1Go before it.
Thanks :)