Opened at 2021-08-16T18:58:31Z
Closed at 2021-08-18T15:06:03Z
#3764 closed task (fixed)
Add standard interaction patterns to GBS HTTP protocol spec
Reported by: | itamarst | Owned by: | exarkun |
---|---|---|---|
Priority: | normal | Milestone: | HTTP Storage Protocol |
Component: | unknown | Version: | n/a |
Keywords: | Cc: | ||
Launchpad Bug: |
Description
The HTTP protocol spec includes a number of endpoints, but doesn't really document the interaction patterns.
For example, one can create a storage index, create a lease on a storage index, write to a share in a storage index, renew a lease... It's not immediately clear which order these operations happen in.
Some example sessions, "here's how you create an immutable", "here's how you renew it", "here's the same for mutable", "here's how you update an immutable", will make the spec clearer and probably be useful in nailing down details about things like endpoint error codes.
Change History (2)
comment:1 Changed at 2021-08-17T18:08:50Z by exarkun
comment:2 Changed at 2021-08-18T15:06:03Z by GitHub <noreply@…>
- Resolution set to fixed
- Status changed from new to closed
In 28758b81/trunk:
I made a start on this at https://github.com/tahoe-lafs/tahoe-lafs/pull/1105