[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:  nobody
         Type:  enhancement   |     Status:  new
     Priority:  major         |  Milestone:  2.0.0
    Component:  code-storage  |    Version:  1.2.0
   Resolution:                |   Keywords:  standards gsoc http
Launchpad Bug:                |
------------------------------+---------------------------------
Changes (by zooko):

 * owner:  taral => nobody


Comment:

 We put review comments over on github:

 * https://github.com/warner/tahoe-
 lafs/commit/c6dd8c4ec5447be14dee122ee7118d98aec7db1e#commitcomment-4376234
 * https://github.com/warner/tahoe-
 lafs/commit/22e2d0010b407a028fabc6a76ff6f8cbbca28558#commitcomment-4376237
 * https://github.com/warner/tahoe-
 lafs/commit/af4669932371c7788ab1bbd36e50c17c9c239f19
 * https://github.com/warner/tahoe-
 lafs/commit/3f6e2f196dc654b8f846b2bc0d174382bf6d59c5#commitcomment-4376381

 It depends on a use of the HTTP Content-Range header which is
 (unfortunately) explicitly forbidden by the HTTP/1.1 spec, so that
 probably needs to change.

 It doesn't have unit tests.

 Other than that, it is awesome!

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