[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:  zooko
         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 zooko):

 Replying to [comment:33 simeon]:
 > Let me know if you think I am beating a different path, and that summary
 can be put somewhere else where it won't clutter your system. :)

 Um, hey man, thanks for your interest! I appreciate the time you are
 taking to share your thoughts about this topic.

 So, I haven't taken the time to read all of your comments here, but I did
 skim through them briefly and I didn't notice anything obviously crazy or
 stupid in the random sampling of sentences that I saw as I skimmed.

 Now, this ticket — about using HTTP for the LAFS storage server protocol —
 is definitely not the best place for people to find your ideas and give
 you feedback on them. They are apparently an alternative to LAFS or a
 possible future variant of LAFS, so maybe one good place would be to post
 the design as a letter to the tahoe-dev mailing list. Other possibilities:
 the p2p-hackers mailing list (http://lists.zooko.com/mailman/listinfo/p2p-
 hackers), or Jack's
 (http://lists.randombit.net/mailman/listinfo/cryptography), or Perry's
 (http://www.metzdowd.com/mailman/listinfo/cryptography) crypto mailing
 lists.

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