|
Author |
Thread Statistics | Show CCP posts - 29 post(s) |
Aethlyn
EVE University Ivy League
194
|
Posted - 2013.03.11 15:40:00 -
[1] - Quote
Sounds interesting. I just hope you include your own torrent handling and don't use any abomination such as that dreaded Pando Media Booster. :)
Also, I'd suggest by default the launcher should ask on first start, whether it should use bittorrent connections or just classic HTTP, because at least in Germany, some ISPs (like universities or some mobile providers) don't like to see P2P traffic and will rightout block, slowdown or sanctionize it (e.g. by cutting your internet access if there're too high P2P Transfers). Always think of unaware/non-savy computer users/players. Looking for more thoughts? Read http://aethlyn.blogspot.com/ or follow me on http://twitter.com/Aethlyn. |
Aethlyn
EVE University Ivy League
197
|
Posted - 2013.03.11 16:03:00 -
[2] - Quote
SamuraiJack wrote:That alone makes CCP's implementation of this much better than most Torrent installers. Flooding out your upstream just throttles your connection as you cannot send commands due to data floods. Shame Blizzard never took that onboard. From my experience over the past years, I really think that's intentional and not just happens: Your download slows down as you Approach 99% and the last few bytes take forever (at least for me; not talking about SC2/D3 patching; only their standalone torrent stuff). Once your sharing ratio approaches 1.0 the last few bytes are completed. Something like that is really stupid, especially for people on asynchronous lines (e.g. my upstream is less than 10% of my downstream). Luckily you could trick their implementation by simply restarting the client. Looking for more thoughts? Read http://aethlyn.blogspot.com/ or follow me on http://twitter.com/Aethlyn. |
Aethlyn
EVE University Ivy League
197
|
Posted - 2013.03.11 16:09:00 -
[3] - Quote
Remiel Pollard wrote:As far as I'm aware, if P2P traffic is encrypted, ISP's can't read it as P2P traffic and cannot throttle it. If you use data encryption, it should work fine. Unfortunately, it's not that easy. There are still obvious things happening like high upload and (possibly) many outbound connections at the same time. Also encryption slows down the whole thing and makes it more CPU intensive, because the data has to be en-/decrypted as well. A simple toggle to select the download strategy is a lot easier to implement and use (even if you only use HTTP you still get the error checking, file verification, etc.). Looking for more thoughts? Read http://aethlyn.blogspot.com/ or follow me on http://twitter.com/Aethlyn. |
Aethlyn
EVE University Ivy League
199
|
Posted - 2013.03.11 17:25:00 -
[4] - Quote
Bienator II wrote:Aethlyn wrote:SamuraiJack wrote:That alone makes CCP's implementation of this much better than most Torrent installers. Flooding out your upstream just throttles your connection as you cannot send commands due to data floods. Shame Blizzard never took that onboard. From my experience over the past years, I really think that's intentional and not just happens: Your download slows down as you Approach 99% and the last few bytes take forever (at least for me; not talking about SC2/D3 patching; only their standalone torrent stuff). Once your sharing ratio approaches 1.0 the last few bytes are completed. Something like that is really stupid, especially for people on asynchronous lines (e.g. my upstream is less than 10% of my downstream). Luckily you could trick their implementation by simply restarting the client. this isn't the fault of the protocol, its the client. Clients try to maintain 1.0 share ratio to keep the network healthy. In CCPs case its entirely different. The network is always healthy since CCP will obviously keep the servers up which upload 24/7. maybe i am wrong but i don't think that CCP wants to use bittorrent because they have bandwidth issues on patch day - it really sounds like all they want is a more reliable protocol.
Of course, it is a thing of the client. This is also something I tried to say. I know there's nothing like that in the basic protocol. Looking for more thoughts? Read http://aethlyn.blogspot.com/ or follow me on http://twitter.com/Aethlyn. |
|
|
|