"""The actual retrieval of the various status parameters (infohash, name, This allows flexible use of status information in other parts of """A callback function can be provided to which status updates are pushed On disk can be scanned on startup to automatically add torrents to the mediaspace. """Creates a new P2P Mediaspace class instance, which maintains allĬontent that is downloaded and/or shared. _init_(cache_dir, status_update_interval, read_cache) ![]() The full API for version 3 is as follows: From the user perspective, these activities happen âunder the hoodâ. A user doesnât have to know anything about torrent files. Instead of the user controlling a torrent-based application, it will be the Fusion application and Semantic Overlay that call the appropriate functions. Important differences are that torrent-files will be created automatically upon injecting content, and that it should be possible to download parts of (some) movies using time codes. The API has a strong resemblance in functionality to the common UI controls of a P2P client. This represents all the files that the Fusion application is âaware ofâ locally and at a P2P network level. The P2P core maintains a list of torrents that contains all the torrents added but not removed. Torrent-files are in essence just small files with metadata, and can be easily included in the metadata that is managed by the Semantic Overlay. A torrent-file can represent a single file or a directory tree containing multiple files. We assume that torrent-files (â.torrentâ) are used as unique identifiers of physical files in the P2P network. We will give an overview of the P2P Mediaspace API that is available for P2P Fusion developers. More detailed information about the BitTorrent protocol and a full specification are available on various websites, e.g., , . The set of all peers currently actively exchanging pieces of the file is called the file's swarm. Once the peer has obtained the complete file it will become a seeder and altruistically provide pieces to other peers without any return. These policies for piece selection and bandwidth trading lead to a balanced economy with suppliers meeting demand and achieving their own goal (fast download) at the same time. By always selecting a rare part of the file from the pieces on offer, a peer ensures it always has a piece of the file that other peers are interested in. By monitoring the download rate obtained from its current set of peers and randomly trying other peers to see if faster peers are available, a user can maximize its download rate. This tit-for-tat mechanism automatically locks out peers who are unwilling to upload themselves. If so, the contacted peer sends a few blocks of the negotiated piece, and continues to do so as long as the other does the same. With this piece in hand, the peer starts to contact other peers in the list to see if they will trade its piece for another part of the file. ![]() Next, the peer contacts a random peer to obtain a first piece of the file itself. The peer then contacts the tracker to obtain a list of peers currently involved in downloading the file, implying they have pieces of the file to share. The metafile gives the peer the address of a tracker for the file and checksums to verify downloaded parts of the file. ![]() A peer wishing to download a particular file through BitTorrent first needs to obtain a torrent metafile for the file from, for example, a Web site or RSS news feed, or via the P2P Fusion platform. Furthermore, for developers interested in the low-level networking details, we will also provide an overview of the Tribler core and its architecture.īitTorrent has an interesting design that enables each individual downloader to maximize his own download rate and locks out users who do not contribute to the system. In the following sections we will give an overview of BitTorrent and of the P2P Mediaspace API. The P2P Mediaspace API tailors the Tribler core for specific use in the P2P Fusion platform. The Tribler core extends the functionality of BitTorrent to make it more generic, more secure, more reliable, and more flexible for use in other applications. The P2P Mediaspace is based on the Tribler P2P Core, which in turn is based on the BitTorrent protocol, a well-known protocol for P2P file transfers based on piece-wise exchange of content. The other parts of the P2P Fusion software use the API of the P2P Mediaspace to perform tasks such as injecting files, downloading files, and acquiring status information about running downloads. The P2P Mediaspace in the P2P Fusion platform is responsible for the actual transfer and management of large pieces of content (most importantly audio and video).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |