Checkpoint audio-only Skald fork work
This commit is contained in:
+4
-4
@@ -7,19 +7,19 @@ users. For example, in order to create a hall, a client may do
|
||||
Content-Type: application/json
|
||||
If-None-Match: *
|
||||
|
||||
The `If-None-Match` header avoids overwriting an existing group.
|
||||
The `If-None-Match` header avoids overwriting an existing hall.
|
||||
|
||||
In order to edit a hall definition, a client first does
|
||||
|
||||
GET /skald-api/v0/.halls/hallname/
|
||||
|
||||
This yields the hall definition and an entity tag (in the ETag header).
|
||||
The client then modifies the group defintion, and does
|
||||
The client then modifies the hall definition, and does
|
||||
|
||||
PUT /skald-api/v0/.halls/hallname/
|
||||
If-Match: "abcd"
|
||||
|
||||
where "abcd" is the entity tag returned by the GET request. If the group
|
||||
where "abcd" is the entity tag returned by the GET request. If the hall
|
||||
definition has changed in the meantime, the entity tag will no longer be
|
||||
valid, and the server will fail the update, which avoids losing an update
|
||||
in the case of a concurrent modification.
|
||||
@@ -46,7 +46,7 @@ allowed methods are HEAD and GET.
|
||||
Returns a list of halls, as a JSON array. The only allowed methods are
|
||||
HEAD and GET.
|
||||
|
||||
### Group definition
|
||||
### Hall definition
|
||||
|
||||
/skald-api/v0/.halls/hallname
|
||||
|
||||
|
||||
Reference in New Issue
Block a user