View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007587 | Taler | libeufin (general) | public | 2023-01-14 10:04 | 2023-09-03 18:14 |
| Reporter | MS | Assigned To | Antoine A | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Target Version | 0.9.4 | ||||
| Summary | 0007587: General pass to potentially switch "200 OK" to "204 No Content". | ||||
| Description | The Taler Wire Gateway API got already changed here: 0676e25980a8b.. This report contiues: 0007301. | ||||
| Tags | No tags attached. | ||||
|
|
What's the rationale for this? It's clearly not a performance issue, why are we complicating the API with different types of responses (empty list vs. 204) to indicate zero transactions? |
|
|
Discussed with Christian: The idea is that 204 indicates that there are no new transactions *and the client should go into long-polling*, while we expect 200 only when transactions are present. While I still think that this is an over-optimization, we should still consistently apply what we've agreed on. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-01-14 10:04 | MS | New Issue | |
| 2023-04-13 20:50 | Florian Dold | Project | libeufin => Taler |
| 2023-04-14 14:30 | Florian Dold | Category | other => libeufin (general) |
| 2023-04-17 11:04 | Florian Dold | Note Added: 0020099 | |
| 2023-04-17 11:04 | Florian Dold | Target Version | => 0.9.3 |
| 2023-04-23 19:36 | Florian Dold | Note Added: 0020133 | |
| 2023-04-23 19:36 | Florian Dold | Assigned To | => MS |
| 2023-04-23 19:36 | Florian Dold | Status | new => assigned |
| 2023-06-30 11:17 | MS | Target Version | 0.9.3 => 0.9.4 |
| 2023-09-03 18:14 | Christian Grothoff | Assigned To | MS => Antoine A |
