tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

add notes 

[Imported from Trac: page UseCases, version 14]
zooko 2008-03-13 04:34:10 +00:00
parent 2f8106ed35
commit bb16a3bd21
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
UseCases.md

@ -29,7 +29,7 @@ Here are some archetypal roles:
* The *Available Migrator* consumes storage from a changing address.
* **Migration Pattern Availability** - Availability is high, but address changes are frequent.
* Examples: Laptops, mobile devices, poor DHCP configurations.
* Should this role supply storage? If so, how does it affect average file availability? -reliability?
* We think that the foolscap/introducer mechanism will dynamically adjust to the changing IP address and make this appear to be a server with good availability, but this use case hasn't been much tested. Please let us know if you try it.
* The *Ephemeral Consumer* consumes storage, but lacks availability.
* **Poor availability** - Availability is low, such as a node that is only up when consuming storage service.