Changes between Version 3 and Version 4 of Ticket #3773


Ignore:
Timestamp:
2021-08-18T15:32:20Z (3 years ago)
Author:
itamarst
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3773 – Description

    v3 v4  
    222. Cancelling leases is not actually supported.
    333. The way lease renewal secrets are generated is likely to change in the switchover from foolscap to HTTP.
    4 4. Internally, the server _already_ treats renewing a lease as potentially adding a new one if renewal fails.
     44. Internally, the server _already_ treats adding a lease as potentially just renewing a lease.
    55
    66As such, the distinction between adding a lease and renewing a lease is unnecessary (presuming item 4 is actually correct!). We would like to simplify HTTP protocol by removing it, and we need to make sure server can gracefully handle clients switching their renewal secret.
    … …  
    99
    10101. Validate item 4 above, since it's critical requirement for the rest of this.
    11 2. In Foolscap client, switch to only using renewal code path.
    12 3. Make sure server creating new lease when renewal fails is well tested, so users don't lose data.
     112. In Foolscap client, switch to only using add lease code path.
     123. Make sure server creating renews lease in add path.
    13134. On server-side, leave new lease Foolscap endpoint in place for backwards compat.
    14145. In new GBS HTTP protocol spec, switch to a single end point for lease creation/renewal, and remove all references to lease cancellation secret.