Author: alanmc
Date: 2008-02-17 18:04:07 -0500 (Sun, 17 Feb 2008)
New Revision: 96011
Modified:
trunk/bitsharp/src/MonoTorrent/MonoTorrent.Client/Managers/ChokeUnchokeManager.cs
Log:
Dont reset PiecesSent to zero.
Modified:
trunk/bitsharp/src/MonoTorrent/MonoTorrent.Client/Managers/ChokeUnchokeManager.cs
===================================================================
---
trunk/bitsharp/src/MonoTorrent/MonoTorrent.Client/Managers/ChokeUnchokeManager.cs
2008-02-17 22:59:25 UTC (rev 96010)
+++
trunk/bitsharp/src/MonoTorrent/MonoTorrent.Client/Managers/ChokeUnchokeManager.cs
2008-02-17 23:04:07 UTC (rev 96011)
@@ -196,10 +196,6 @@
//We're already choking this peer, nothing to do
return;
- // FIXME: This doesn't need to be done anymore. This was a
horrible hack
- // so i could implement a 'stupid' choke/unchoke algorithm. The
new algorithm doesn't
- // use this, so don't reset down to zero :)
- peer.Connection.PiecesSent = 0;
peer.Connection.AmChoking = true;
owningTorrent.UploadingTo--;
RejectPendingRequests(peer);
@@ -499,7 +495,6 @@
//We're already unchoking this peer, nothing to do
return;
- PeerToUnchoke.Connection.PiecesSent = 0;
PeerToUnchoke.Connection.AmChoking = false;
owningTorrent.UploadingTo++;
PeerToUnchoke.Connection.EnqueueAt(new UnchokeMessage(), 0);
_______________________________________________
Mono-patches maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-patches
