Differences between revisions 6 and 7
Revision 6 as of 2006-03-08 18:55:08
Size: 1455
Editor: TFKyle
Comment:
Revision 7 as of 2006-03-18 04:17:15
Size: 1475
Editor: TFKyle
Comment:
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
BitDaemon will use the people.tfkyle.BitDaemon D-Bus message bus name, there will be one Global interface "people.tfkyle.BitDaemon" at path /people/tfkyle/BitDaemon, and multiple "people.tfkyle.BitDaemon.Torrent" interfaces on the paths "/people/tfkyle/BitDaemon/Torrents/<torrent UUID>" where the torrent UUID is a uuid generated when adding a torrent BitDaemon will use the org.dyndns.tfkyle.BitDaemon D-Bus message bus name, there will be one Global interface "org.dyndns.tfkyle.BitDaemon" at path /org/dyndns/tfkyle/bitdaemon, and multiple "org.dyndns.tfkyle.BitDaemon.Torrent" interfaces on the paths "/org/dyndns/tfkyle/bitdaemon/torrents/<torrent UUID>" where the torrent UUID is a uuid generated when adding a torrent

BitDaemon

BitDaemon will be a BitTorrent client which runs as a daemon allowing multiple clients to connect to it and control it, but for now its just a set of ideas. at the moment this page is just a scratch pad describing those ideas

Current Planned Deps:

Communication between it and its clients will happen via. a defined DBus interface (there might be a current Draft of the interface spec in /SpecDraft)

Tracker communication will use libTorrent

Hooks: Hooks allow you to run anything when something happens, for example when a download finishes, BitDaemon should implement hooks in 2 ways:

D-Bus interface

BitDaemon will use the org.dyndns.tfkyle.BitDaemon D-Bus message bus name, there will be one Global interface "org.dyndns.tfkyle.BitDaemon" at path /org/dyndns/tfkyle/bitdaemon, and multiple "org.dyndns.tfkyle.BitDaemon.Torrent" interfaces on the paths "/org/dyndns/tfkyle/bitdaemon/torrents/<torrent UUID>" where the torrent UUID is a uuid generated when adding a torrent

BitDaemon (last edited 2008-02-05 05:46:33 by localhost)