Quote:
Originally Posted by eschwartz
I don't know how much benefit there is, but there is very little cost
|
What happens to an existing swarm when I do a re-release because of a bug? I dont know of any way to handle that in torrent, except by bumping the version number and filename, which would actually lead to more update notifications, which was why this whole thread started in the first place.
With HTTP downloads, any in-progress downloads complete nicely in case of a re-release thanks to the way files work in linux.
The only way to handle that, that I can see would be to change the update notification code in calibre to not notify about x.y.
z version bumps.
Then there is the inevitable feature requests I will get from linux users, asking for a way to use the torrents in the linux installer.
Then there is the fact that torrent downloading breaks download counts, something I like to track. I dont see anyway around that short of setting up a proper torrent seed server as opposed to using web seeding. More costs.
These things are never quite as simple as they appear at first glance.