by mheydt
25.
September 2007 15:54
>
I want the operation of trackers in iCity to be more robust than in normal bittorrent clients. In a normal bittorrent network, a client opens a torrent file which has the address of a tracker for that particular torrent, and the client connects to that tracker. The tracker is typically a dedicated server system that coordinates communications amongst peers and may not actually share the file itself, but simply manage a client finding other clients in the network.
This makes it such that the tracker system must be online all of the time, and at a particular location (address) in the network. This is disadventagoues for several reasons, including that 1) if the tracker goes offline, all communications cease (single point of failure), and that a client cannot always itself host tracking services. The latter point is important as without the capability of tracking items you share, you must upload the torrent file to the tracker system for hosting which involves additional steps and gets you into the tracker availability situation previoiusly mentioned.
What I propose as an implementation of tracking in iCity is the following:
1) Any node can spin up a tracker at any time and track their own shares of packages.
2) Any node can be configured with the identity of other tracker nodes in the iCity community. They can contact those trackers and download a torrent file to download the desired file using that tracker.
3) If not desirous of self hosting a tracker, the node can ask other nodes (in particular other dedicated trackers) to host tracking for a package. Note that this can be multiple systems to have redundant trackers to provide for greater availability.
4) If not being able to connect to any trackers for a particular package, the node can query other nodes in the community for tracking services for the package and connect to any of them.
In all, this does not change the model of tracking or the protocols involved in bittorrent tracking. It does however build an overlay p2p network to faciliate distribution and access of tracking services for content in the community.
0f6810ca-ad1b-4009-8df5-c5d29cefa4e8|0|.0
Tags:
iCity | p2pSB