170 | | Now it's time for a bit of litterature. |
171 | | |
172 | | TODO |
| 170 | Now it's time for a bit of litterature. File capabilities are unique "keys" |
| 171 | associated with the files. It's used internally by Tahoe-LAFS to identify |
| 172 | every file, and used as an URL to locate the file. |
| 173 | |
| 174 | For immutable files, capabilities are like hash table keys, they match |
| 175 | a unique file. A single bit difference between two files will give two |
| 176 | different capabilities. |
| 177 | |
| 178 | For mutable files, there are read-only and read-write capabilities. |
| 179 | A read-only capability will point to a version of a file. A read-write |
| 180 | capability represant the ability to read the file, the ability to write |
| 181 | a new version of a file. |
| 182 | |
| 183 | for more informations, look at Capabilities section of : |
| 184 | http://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/architecture.txt |