| 5 | | 3. Foolscap connections still preserve current semantics, for backwards compat with existing clients: new uploads start from scratch. However, the implementation happens in a different place, instead of happening automatically on disconnect it happens as part of `allocate_buckets()`. |
| 6 | | 4. `allocate_buckets()` external behavior remains unchanged. |
| | 5 | 3. `allocate_buckets()` maintains same external behavior. |
| | 6 | 4. Foolscap connections specifically still preserve current semantics, for backwards compat with existing clients: disconnection causes cancellation. |
