Changeset 11162
- Timestamp:
- 06/24/09 18:41:20 (9 months ago)
- Files:
-
- 1 modified
-
dotorg/trunk/html/beps/bep_0003.rst (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
dotorg/trunk/html/beps/bep_0003.rst
r11031 r11162 7 7 Type: Standard 8 8 Created: 10-Jan-2008 9 Post-History: 9 Post-History: 24-Jun-2009, clarified the encoding of strings in torrent files 10 10 11 11 BitTorrent is a protocol for distributing files. It identifies content … … 17 17 18 18 A BitTorrent file distribution consists of these entities: 19 ---------------------------------------------------------- --19 ---------------------------------------------------------- 20 20 21 21 - An ordinary web server … … 82 82 This maps to a dictionary, with keys described below. 83 83 84 The ``name`` key maps to a string which is the suggested name85 to save the file (or directory) as. It is purely advisory.84 The ``name`` key maps to a UTF-8 encoded string which is the 85 suggested name to save the file (or directory) as. It is purely advisory. 86 86 87 87 ``piece length`` maps to the number of bytes in each piece … … 113 113 ``length`` - The length of the file, in bytes. 114 114 115 ``path`` - A list of strings corresponding to subdirectory115 ``path`` - A list of UTF-8 encoded strings corresponding to subdirectory 116 116 names, the last of which is the actual file name (a zero length list 117 117 is an error case). … … 119 119 In the single file case, the name key is the name of a file, in the 120 120 muliple file case, it's the name of a directory. 121 122 All strings in a .torrent file that contains text must be UTF-8 123 encoded. 124 121 125 122 126 Tracker GET requests have the following keys:
