View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005506 | Taler | specification | public | 2019-01-08 17:33 | 2024-01-12 13:03 |
| Reporter | Marcello Stanisci | Assigned To | Christian Grothoff | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | low | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | won't fix | ||
| Product Version | git (master) | ||||
| Target Version | 0.6 | Fixed in Version | 0.6 | ||
| Summary | 0005506: Should "last_issue_date" screen signkeys as well? | ||||
| Description | The current API lets "/keys?last_issue_date=XXX" screen *only* denomination keys per their timestamp. Shall this timestamp-based screening happen for signkeys as well? Although this suggested change doesn't improve significantly performance - signkeys are just "little" - it might save the user from getting confused by seeing only one type of key being screened, and not all of them. | ||||
| Tags | No tags attached. | ||||
| I've checked, and this is actually not easily (or sanely) doable. for signing keys, we return the current one and those "a bit into the future", but the "bit into the future" can change depending on the exchange configuration. Also, in any case, this should only ever return a handful of keys. So doing this *brittle* optimization to possibly save a few bytes of bandwidth makes no sense. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-01-08 17:33 | Marcello Stanisci | New Issue | |
| 2019-01-08 17:33 | Marcello Stanisci | Status | new => assigned |
| 2019-01-08 17:33 | Marcello Stanisci | Assigned To | => Christian Grothoff |
| 2019-01-08 17:33 | Marcello Stanisci | Priority | normal => low |
| 2019-01-08 18:00 | Christian Grothoff | Note Added: 0013448 | |
| 2019-01-08 18:00 | Christian Grothoff | Status | assigned => informing |
| 2019-01-08 18:00 | Christian Grothoff | Resolution | open => won't fix |
| 2019-01-08 18:00 | Christian Grothoff | Fixed in Version | => 0.6 |
| 2019-01-08 18:00 | Christian Grothoff | Severity | minor => feature |
| 2019-01-08 18:00 | Christian Grothoff | Product Version | => git (master) |
| 2019-01-08 18:00 | Christian Grothoff | Target Version | => 0.6 |
| 2019-12-20 18:12 | Christian Grothoff | Status | informing => closed |
| 2024-01-12 13:03 | Christian Grothoff | Category | exchange API (HTTP specification) => specification |