From bb16a3bd21d478d5277457591687e0713b859a45 Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Thu, 13 Mar 2008 04:34:10 +0000
Subject: [PATCH] add notes

[Imported from Trac: page UseCases, version 14]
---
 UseCases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/UseCases.md b/UseCases.md
index f52cfa0..f8b29df 100644
--- a/UseCases.md
+++ b/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.