[tahoe-lafs-trac-stream] [tahoe-lafs] #393: mutable: implement MDMF

[tahoe-lafs]

#393: mutable: implement MDMF
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  zooko
         Type:           |     Status:  new
  enhancement            |  Milestone:  1.9.0
     Priority:  major    |    Version:  1.0.0
    Component:  code-    |   Keywords:  newcaps performance random-access
  mutable                |  privacy gsoc mdmf mutable backward-
   Resolution:           |  compatibility forward-compatibility review-
Launchpad Bug:           |  needed
-------------------------+-------------------------------------------------

Comment (by davidsarah):

 In [source:ticket393-MDMF-2/src/allmydata/mutable/filenode.py at 5187#L682
 MutableFileNode]:
 {{{
     def _upload(self, new_contents, servermap):
         """
         A !MutableFileNode still has to have some way of getting
         published initially, which is what I am here for. After that,
         all publishing, updating, modifying and so on happens through
         !MutableFileVersions.
         """
         assert self._pubkey, "update_servermap must be called before
 publish"
 }}}
 Is this comment correct? I thought {{{upload}}} (which calls
 {{{_upload}}}) was supposed to work whether or not there is an existing
 version.

 Also, the message in the assertion should be "_update_servermap must be
 called before _upload", I think.

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