BitTorrent Queue Manager

It was about a month since BTQueue 0.1.2 released last month. I would like to introduce BTQueue 0.1.3 which is actually a minor bug fixes version with several features added. In this version “peer” command is back again. You can query the latest peer list replied by the tracker anytime you like. In addition, I added “eval” command that allows you to view or modify data in memory on the fly. This function will be very useful if you are Python programmers. Since I have just gotten a chance to use DHT, it is possible to force DHT by setting local policy; otherwise, DHT will be forced if the announce URL starts with udp://. The option –saveas has been fixed to work as except. One more thing, IP to Country database has been updated to include up-to-date mapping.

In conclusion, I do recommend all you to upgrade as soon as possible the get the most stable version of BTQueue. I released RPM in 2.2, 2.3 and 2.4. Please use the right one for your distribution. Lastly, don’t forget to leave your comments and bugs at http://www.howforge.com/forum. My plan is to integrate BitTorrent 4.20.0 into BTQueue 0.1.4 within next month.

Technorati Tags: btqueue, bittorrent, python, dht, p2p

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. For more information, don’t forget to read my blog at HowForge.com.

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