4 ms·
> You could wrap the FUSE client in some basic logic that detects newer torrents on the server and reloads/remounts. Wouldn't creating new torrents for each u
by elevation 2y ago
> You could wrap the FUSE client in some basic logic that detects newer torrents on the server and reloads/remounts.
Wouldn't creating new torrents for each update to a dataset cause clients to retransfer data that hasn't changed?
- nine_k 2y agoI suppose blocks with the same hash as existing won't get re-requested.
- raffraffraff 2y agoFrom memory, with a standard torrent, when it loads up a new torrent file it verifies hashes on existing data, and if it matches up it leaves it. That's how it worked on my old distribution. Not sure how this would work on BTFS, but if it's lazy-loading data and if it handled existing data in the same way, it shouldn't be an issue. But I think this would suit infrequently changing data anyways.