Changes between Version 10 and Version 11 of Ticket #3901


Ignore:
Timestamp:
2023-01-23T14:12:30Z (2 years ago)
Author:
itamarst
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3901 – Description

    v10 v11  
    442. #3912: Storage nodes send the NURL to an introducer, in addition to the fURL for legacy Foolscap protocol. This is sent as an announcement upgrade so it supercedes existing announcement.
    553. #3783: The introducer sends NURLs to storage clients. INVARIANT: old storage clients can safely get and ignore NURLs. If this is not the case, some conditional logic needs to be introduced so old clients don't get NURLs. It seems like this will just happen automatically, and moreover the announcement is just a dictionary with random keys, so hopefully will Just Work once #3912 is done.
    6 4. The storage client understands NURLs, and use HTTP protocol instead of Foolscap when possible. See design doc for further discussion (QUESTION: is it actually possible to say "this furl and nurl are for the same server"? technically, maybe but not necessary given announcement upgrades).
     64. DONE. The storage client understands NURLs, and use HTTP protocol instead of Foolscap when possible. See design doc for further discussion (QUESTION: is it actually possible to say "this furl and nurl are for the same server"? technically, maybe but not necessary given announcement upgrades).
    775. Currently the storage client caches per-server FURLs indefinitely. New clients should check with introducer if a NURL (HTTP) has replaced a FURL (Foolscap) and update appropriately.
    886. The client may only have FURL, and not have introducer. For that situation the Foolscap protocol should grow a away for clients to get new URLs (`remote_get_version`?)