Either way, i would guess my stuff integrates too deeply to make use of those modules (at least not easily), plus i already have a LONG list of dependancies
Thanks for the link though, I will check them out and see how i go!
Actually, the JSON-rpc-spec is the most user friendly. All libraries are an abstraction in one way or another. The main issue of the spec is that you have to follow the references to the source of transmission itself. The spec of the status has changed in 1.42. https://github.com/killemov/Shift ...
I'm looking for some documentation on the JSON API and what codes I can expect + what they mean. I'm in the process of converting my web interface over from using transmission-remote calls and scraping / regex'ing the return to actuallly making direct calls via JSON to the RPC (in reality ...
Hopefully i can help you out here, i have just spent about an hour and a bit trying to get this to work myself, and what i found was:
even though i had libevent 1.4.1 installed via RPM, pkg-config was not detecting it at all (no pc file anywhere in pkg-configs path) (check yours with pkg ...
I have a torrent running, and remote is showing it with an asterisk, which seems to mean error, when i do a debug, the error code is 13, but with no description.
I cant figure out what it seems to think is wrong, i have checked in the web interface too, and it does not seem to recognise ...