View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008001 | Taler | exchange | public | 2023-12-06 11:45 | 2024-01-12 14:18 |
| Reporter | oec | Assigned To | oec | ||
| Priority | low | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0008001: TEH_extension_post_handler: ensure idempotency | ||||
| Description | The POST-handler for extensions deals with incoming JSON-data - a proof-of-fulfillment of a policy - and policy-data from the database. In the case that the policy already has been sucessfully fulfilled, we might want to 1. make sure that the incomming fulfillment data is the same as the stored, otherwise return an conflict 2. return success early, without executing the policy-exention-handler This approach needs more careful thought out, refined and designed, based on the concrete use-cases we have for policy extensions so far: escrow, refund and auctions. | ||||
| Tags | design, policy-extensions | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-12-06 11:45 | oec | New Issue | |
| 2023-12-06 11:45 | oec | Status | new => assigned |
| 2023-12-06 11:45 | oec | Assigned To | => oec |
| 2023-12-06 11:45 | oec | Tag Attached: design | |
| 2023-12-06 11:45 | oec | Tag Attached: policy-extensions | |
| 2023-12-23 16:57 | Christian Grothoff | Target Version | 1.0 => post-1.0 |
| 2024-01-12 14:18 | oec | Relationship added | child of 0008075 |
