Opened 14 years ago

Closed 13 years ago

Last modified 10 years ago

#220 closed Enhancement (fixed)

Lazy Bitfields

Reported by: SoftwareElves Owned by: somebody
Priority: Normal Milestone: 1.40
Component: libtransmission Version: 0.6
Severity: Normal Keywords:
Cc:

Description

Description found on http://www.azureuswiki.com/index.php/Commandline_options: Always send a faked incomplete bitfield, and instead send remaining completed piece info via Have messages. Certain ISP (ie Cablevision's Optimum Online) networks seem to block peer seeding via "complete" bitfield message filtering. You should only use this option if you need to.

Added to that list of bad ISP is the very popular Comcast, which has cause alot of "my torrent's aren't seeding" in the forum. If i remember correctly, the client sends 12 random undownloded blocks in it's bitfield to each peer when it is seeding.

Change History (8)

comment:1 Changed 14 years ago by charles

  • Priority changed from Highest to High
  • Severity changed from Blocker to Normal

This would be nice to have... but it's not a blocker IMO

comment:2 Changed 14 years ago by charles

  • Type changed from Defect to Enhancement

comment:3 Changed 14 years ago by SoftwareElves

  • Resolution set to wontfix
  • Status changed from new to closed

encryption > lazybitfields, no need for it any more

comment:4 Changed 13 years ago by charles

  • Milestone changed from Sometime to 1.40
  • Resolution wontfix deleted
  • Status changed from closed to reopened

It appears that lazy bitfields are still useful in some circumstances, and it's very easy to implement.

comment:5 Changed 13 years ago by charles

  • Priority changed from High to Normal

first draft of supporting this is now in r6556.

We'll still need to add support for setting this in the GUIs and in transmission-remote.

The gtk+ and daemon clients can be used with this right now by editing the "lazy-bitfields-enabled" key in settings.json.

comment:6 Changed 13 years ago by charles

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:7 Changed 12 years ago by charles

  • Component changed from Transmission to libtransmission

comment:8 Changed 10 years ago by jordan

This feature has been removed from trunk. Encryption and the "fast" extensions' have_all / have_none messages have made this feature obsolete.

Actually this feature has been broken for quite awhile because anytime we had a seed, a have_all message was sent instead of a lazy bitfield, and nobody noticed...

Note: See TracTickets for help on using tickets.