API v0: make lastmod settable via API #13

Open
opened 3 years ago by tdemin · 0 comments
tdemin commented 3 years ago
Owner

Setting it via API prevents various race conditions, where server last modification date is different from what the client has, potentially overriding other clients' data.

This means Amber stops updating lastmod internally and instead accepts it as a settable field.

This affects POST /task and PATCH /task/[id].

Setting it via API prevents various race conditions, where server last modification date is different from what the client has, potentially overriding other clients' data. This means Amber stops updating `lastmod` internally and instead accepts it as a settable field. This affects `POST /task` and `PATCH /task/[id]`.
tdemin added the
API
label 3 years ago
tdemin self-assigned this 3 years ago
tdemin changed title from Make lastmod settable via API to API v0: make lastmod settable via API 3 years ago
tdemin added the
API v0
label 3 years ago
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: tdemin/amber#13
Loading…
There is no content yet.