diff options
| author |  http://lj.rossia.org/users/imz/ <http://lj.rossia.org/users/imz/@web> | 2012-09-26 18:20:07 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2012-09-26 18:20:07 +0000 |
| commit | cfb060e93b0eb5eef7a9073d6184301fae773472 (patch) | |
| tree | ce4a0356462c433d29a69c4b92ca9f400e3c9b97 /doc/todo/wishlist:_spec.remotes_for_other_peer_network_data_stores___40__gnunet__44___freenet__41__.mdwn | |
| parent | 7de4ce4a86776a0a41e4a0e2d9917795da106c28 (diff) | |
Cf. URNs -- what about extendings keys to URNs? The there's no guarantee that will get the identified content in always the same format.
Diffstat (limited to 'doc/todo/wishlist:_spec.remotes_for_other_peer_network_data_stores___40__gnunet__44___freenet__41__.mdwn')
| -rw-r--r-- | doc/todo/wishlist:_spec.remotes_for_other_peer_network_data_stores___40__gnunet__44___freenet__41__.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/todo/wishlist:_spec.remotes_for_other_peer_network_data_stores___40__gnunet__44___freenet__41__.mdwn b/doc/todo/wishlist:_spec.remotes_for_other_peer_network_data_stores___40__gnunet__44___freenet__41__.mdwn index 33928b6bd..0e3d8ac0a 100644 --- a/doc/todo/wishlist:_spec.remotes_for_other_peer_network_data_stores___40__gnunet__44___freenet__41__.mdwn +++ b/doc/todo/wishlist:_spec.remotes_for_other_peer_network_data_stores___40__gnunet__44___freenet__41__.mdwn @@ -22,4 +22,4 @@ For example: * Similarly, a backend for the hashes used in **BitTorrent** and **magnet links** could be used. If we want a trackerless mode, then probably it's a similar case for a "global"/built-in special remote that needs no local setup in each repo. Using a selected tracker would mean setting up a special remote in our repo. * **Git** itself can be viwed as place to look for the content. There could be a corresponding backend and a builtin special remote (needing no extra setup) to look for the content among the objects stored in the local Git repo. (What if we have a copy of a file that we've put under the control of git-annex in a previous Git commit? We could get it from the object store of Git.) * **Venti**, [[**Tahoe-LAFS**|todo/tahoe lfs for reals]] would need a backend for their hashes, and a specially setup special remote in each repo where we'd like to use them--because these are not "global" system, we must setup the path to the instance of the filesystem we'd like to use. -* probably, there must be other interesting cases of this kind.... (I'm also thinking about using somethng like a bibliogrphic information as a key, but then it wouldn't guarantee identical files: the same paper can be stored in diffrent formats, etc.) +* probably, there must be other interesting cases of this kind.... (I'm also thinking about using somethng like a bibliogrphic information as a key, but then it wouldn't guarantee identical files: the same paper can be stored in different formats, etc. Cf. <http://en.wikipedia.org/wiki/Uniform_resource_name#Examples>, via <http://it.slashdot.org/comments.pl?sid=3032489&cid=40907233>.) |