-Files for which a hash cannot be found should not be added to the DHT.
+Use python-debian for parsing RFC 822 files.
-If the hash can't found, it stands to reason that other peers will not
-be able to find the hash either. So adding those files to the DHT will
-just clutter it with useless information. Examples include Release.gpg,
-Release, Translation-de.bz2, and Contents.gz.
+There are already routines for parsing these files, so there is no need
+to write more. In the AptPackages, change the Release file parsing to
+use the python-debian routines.
Packages.diff files need to be considered.
adding them to the tracking done by the AptPackages module.
-Change file identifier from path to hash.
-
-Some files can change without changing the path, since the file was
-added to the DHT by the peer. Examples are Release, Packages.gz, and
-Sources.bz2. This would cause problems when requesting these files by
-path. Instead, share the files by hash, then the request would be for
-http://127.3.45.9:9977/~<urlencodedHash>, and it would always work. This
-will require a database lookup for every request.
-
-
PeerManager needs to download large files from multiple peers.
The PeerManager currently chooses a peer at random from the list of