Integers, byte-strings, lists, and dictionaries are natively supported. torrent files are bencoded, as well as tracker responses, and Mainline DHT RPC messages. Like JSON, and unlike ProtoBufs, an external schema is not required to decode a bencoded message. bencodingīencoding is a binary format that can store arbitrary byte strings without encoding overhead. The two formats which I think are most promising are bencoding, a binary format, and YAML, a text format. Text format encoders are more complicated and less space efficient, particularly for binary data, however users will be able to read and write encoded files directly. A binary format will be simpler to encode and decode and more space efficient, however users will not be able to read or write encoded files directly. I think the major choice to be made is whether to use a binary format or a text-based format. We'll need to choose a format for storing metadata. This would have the advantage that existing torrents could be annotated without needing to reupload them, although there would be some resource overhead from having to track twice as many torrents.
CEPSTRAL TORRENT TORRENT
In this scheme, torrent A would contain the data itself, and torrent B would contain all the annotated torrent metadata, as well as either the infohash, or the complete.
CEPSTRAL TORRENT SOFTWARE
Non-annotated-torrent-aware software may munge or choke on additional data in metainfoĪnother option is to provide it in a completely different torrent, which references the torrent that actually contains the data. Users of non-annotated-torrent-aware software won't know that the torrent is annotated
Most compact representation, since per-file metadata can appear directly in the file tree entry, instead of having to duplicate it in another structure
Single canonical file containing both torrent metainfo and annotated torrent metadataĪpplication logic simplified, since all metadata downloaded, validated, and stored as a single byte stream
torrent file, verifying metadata is easy, as its hash will appear in the info dictionary.Ĭlients can't skip or delay downloading large pieces of metadataĪll metadata appears in a single file, and so cannot be manipulated with command-line utilities that expect, for example, individual digital signatures or timestampsĪn additional entry in the info dictionary containing data describing the entire torrent, as well as data describing files under their respective file tree entries. If metadata is transmitted out-of-band, for example in a single augmented. Simpler library and application logic compared to a directory torrent.Ī single file in the torrent named annotations.bencode containing all metadata. Will be necessary to define a transformation from directory to bencoded dictionary if we want to define a format that contains both annotated torrent metadata and. If metadata is transmitted out-of-band it will be harder to verify that it has not been tampered with, since it will need to compare hashes of all files in annotations directory to the root hashes in the torrent, instead of needing to compare a single file hash.
CEPSTRAL TORRENT FULL
(This is also a pro of using a single bencoded dictionary.Ĭode dealing with a directory full of files is more complex than that for dealing with a single bencoded object.
CEPSTRAL TORRENT DOWNLOAD
Timestamps, public keys, and digital signatures are relatively small, but if many files are timestamped or signed separately, or if many public keys are included, they may add up.ĭata contained within files on disk, as opposed to appearing as entries in a bencoded dictionary, are easier to interact with manually, for example using command line utilities to verify digital signatures and timestamps.Ī non-annotated-torrent-aware torrent client may be used to download a torrent, after which annotated-torrent-aware software may take over to process the data further, which will be easier of the data appears on disk in the torrent, as opposed to in a separate file. The bulk of the metadata is in annotations/info.bencode, but may also contain additional files such as timestamps, digital signatures, and public keys.Īllows skipping or delaying downloading large pieces of metadata. I see three ways in which metadata may be provided in an annotated torrent: Directory in torrentĪ top level directory in the torrent named annotations. Annotated-torrents's Issues RFC 2: Metadata Layout
0 kommentar(er)
