I’m very proud to announce the release of BTQueue 0.1.2 454. This release is mainly targeted to handling incorrect data sent from some private trackers gracefully. Actually, I was inspired by a post in forum. It turned out that BTQueue can’t talk to some private trackers and raised error message like: bad data from tracker - invalid bencoded value (data after valid prefix). Million thanks to dodgy, I managed to find the problem. Let me give you some example. Assuming that a tracker returns below data after receiving an announce message.

d8:intervali1800e5:peers6:B__}__ee 

Actually, above bencoded data is not absolutely correct. There are too many "e" at the end of this message so the correct one should be as follow.

d8:intervali1800e5:peers6:B__}__e

Most clients don’t care any extra data at the end of messages but BTQueue does. As a result, BTQueue treated this as a totally invalid data and showed you above error message. There are 2 choices to solve this problem. 1) fix the code in all trackers and 2) ignore extra code in BTQueue. Since I can’t force all trackers to fix this problem so it is necessary for me to handle this problem properly by just ignoring extra contents. That’s why I categorized this release as minor feature enhancement instead of minor bug fix.

Technorati Tags: Development, Announcement, English, News, Product, BTQueue, Tips and Tricks