#683: So-called URIs aren't
---------------------+------------------------------------------------------
Reporter: kpreid | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone: undecided
Component: unknown | Version: 1.3.0
Keywords: | Launchpad_bug:
---------------------+------------------------------------------------------
Comment(by kpreid):
To be a little more explicit: in the message Zooko linked to, I allude to
that if Tahoe directories contained general URIs, then you could insert a
directory entry which is a revocable membrane to a Tahoe directory; this
directory entry is not itself a Tahoe-type-URI because Tahoe, being
distributed, cannot support revocation (there is no relied-upon agent in
the grid to remember to abort access).
(This wouldn't just require inserting URIs in tahoe directories, though;
it would also require that clients are willing to switch between the
crypto-and-DHT-based ('offline', in a sense) Tahoe protocols and a talk-
to-one-server-which-proxies-for-you ('online') protocol. But storing URIs
in directories at least lets clients *have the option of being so fancy*.)
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/683#comment:2>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
_______________________________________________
tahoe-dev mailing list
[email protected]
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
