Sugree

skip to navigation

rtorrent is not tough

Actually, my favorite BitTorrent client is BTQueue but the latest version has some memory leak problems for long run which I have no idea how to solve. My plan is to replace its backend to something native because Python memory management is not suitable for long run and heavy memory consumption applications like BitTorrent client. My current backend is rtorrent written by rakshasa on top of libtorrent. Anyway, I unified rtorrent to make it run separately behind BTQueue and let BTQueue talk to rtorrent via XML-RPC. Unfortunately, the new BTQueue is not usable yet so I have to let web-based client to call XML-RPC directly to rtorrent.

XML-RPC APIs of rtorrent is very flexible. I mean too flexible for normal use. Client may specify value name to query. That is my problem. I would like to minimize XML-RPC request so I call a long list of values in a single request. As a result, rtorrent terminates so often . Now my workaround is to separate that long list into 2 short lists and call 2 times. It works! Don't know why but it works.

Submitted by sugree on Sat, 02/16/2008 - 23:55

your first sentence makes me

your first sentence makes me smile :D

That bug is now fixed, so

That bug is now fixed, so any number of calls with multicall, etc, should work.

Post new comment

The content of this field is kept private and will not be shown publicly.
+

Main menu

+++++++++++++++++++++++++++++++