Changes between Version 3 and Version 4 of Ticket #3901


Ignore:
Timestamp:
2022-06-08T19:06:28Z (3 years ago)
Author:
itamarst
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3901 – Description

    v3 v4  
    664. 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.
    8 6. 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.
     86. 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`?)