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"?). |
7 | | 5. Currently the storage client caches per-server FURLs indefinitely. New clients should check if a NURL (HTTP) has replaced a FURL (Foolscap) and update appropriately. |
| 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). |
| 7 | 5. 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. |