[tahoe-lafs-trac-stream] [tahoe-lafs] #510: use plain HTTP for storage server protocol

[tahoe-lafs]

#510: use plain HTTP for storage server protocol
------------------------------+---------------------------------
     Reporter:  warner        |      Owner:  taral
         Type:  enhancement   |     Status:  new
     Priority:  major         |  Milestone:  2.0.0
    Component:  code-storage  |    Version:  1.2.0
   Resolution:                |   Keywords:  standards gsoc http
Launchpad Bug:                |
------------------------------+---------------------------------

Comment (by warner):

 I put a quick prototype of using HTTP to download immutable share data in
 my "http-transport" github branch (https://github.com/warner/tahoe-
 lafs/tree/http-transport , may or may not still exist by the time you read
 this). It advertises a "storage-URL" through the #466 extended introducer
 announcement, and uses the new {{{web.client}}} code in recent Twisted
 (10.0 I think?) and a {{{Range:}}} header to fetch the correct read
 vector. It does not yet use persistent connections, which I think are
 necessary to get the performance improvement we're hoping for. It also
 still uses Foolscap for share discovery (getting from a storage index to a
 list of share numbers on that server), and doesn't touch mutable shares at
 all, and of course doesn't even think about uploads or modifying shares.

 I also added #1565 to discuss the URLs that should be used to access this
 kind of service.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/510#comment:20>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage