Torrent Client

[JAJames]

As a user, I want to be able to download Renegade X patch data using a torrent client, so that I can download from multiple sources simultaneously and not be restricted to the bandwidth available by a single mirror.

As a developer, I want to be able to offload cost of data distribution by partially distributing that responsibility to end users in conjunction with the HTTP mirrors.

Acceptance Criteria:

• [ ] Add TorrentPatchSource class and implementation
• [ ] Mirrors should be able to fully support torrent downloads with no/minimal modification
• [ ] Retain WebPatchSource as failover, for instances where client is unable to use P2P protocols
• [ ] Add Seed Torrent option
• [ ] Seed Torrent option should be disabled by default
• [ ] Clients should always seed the torrent when in the patching process
• [ ] Source displayed on UI should be "Peer-to-Peer" when using TorrentPatchSource

[JAJames]

@craige1 Did I miss anything in the AC that we went over previously?

[JAJames]

Closing this for now, since #12 addressed the performance concerns which this would have resolved. May reopen this in the future if higher priorities are all taken care of.