[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1893: don't do lease-renewal automatically

[Tahoe-LAFS]

#1893: don't do lease-renewal automatically
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:
         Type:           |     Status:  new
  enhancement            |
     Priority:  normal   |  Milestone:  undecided
    Component:  code-    |    Version:  1.9.2
  storage                |   Keywords:  leases garbage-collection
   Resolution:           |  accounting
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by exarkun):

 Separating these actions also makes accounting easier.  "Accept a change
 to a mutable share" and "store some data for a period of time" are
 potentially separate accounting operations.  Combining these in the
 implementation makes it impossible to separate them from each other,
 either in practice or for accounting purposes.

 I think a first step (apart from those outlined by zooko) in this
 direction will be to refactor the implementation so that there is clear
 separation between data service operation (eg writing to a mutable share)
 and the lease operation.  In this first step, there will be no change in
 behavior.  The entrypoint used by clients will behave the same, it will
 just be implemented differently.

 The refactoring will pave the way for a protocol change (later) where
 these operations *can* be invoked separately by clients.  Clients which
 wish to participate in a system that uses some form of accounting can then
 invoke them separately and servers which wish to put such accounting into
 place can reject the combined operation and require clients to perform the
 two parts separately (if, indeed, both parts are desired by the client at
 any particular point in time).

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1893#comment:5>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage