[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2788: cache server information, use later (with overrides)

[Tahoe-LAFS]

#2788: cache server information, use later (with overrides)
------------------------------+-----------------------
     Reporter:  warner        |      Owner:
         Type:  enhancement   |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-network  |    Version:  1.11.0
   Resolution:                |   Keywords:
Launchpad Bug:                |
------------------------------+-----------------------

Comment (by warner):

 I'm changing the PR281 branch to use `safe_dump()`, to avoid this. Thanks
 to dstufft, I'm also modifying the loading side to always give us unicode
 strings, to match what we wrote out.

 In the longer run, I'm still thinking about JSON instead of YAML. On IRC,
 dstufft and simpson were in favor of JSON for machine-written files, but
 either YAML or TOML for files written by humans. (He said that Python is
 likely to be using TOML in the future, and !Rust/Cargo already does).

 What about this: the cache could be in JSON, but the override file could
 be in YAML or TOML? I think we're only going to be putting three things in
 the override file (serverid as the key, FURL and connection-policy as the
 values), so it might not be necessary to copy-and-paste stuff from one to
 the other very much, and YAML/TOML is certainly easier to edit than JSON.

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