View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010914 | Taler | wallet-core | public | 2026-01-25 15:04 | 2026-01-25 15:05 |
| Reporter | Christian Grothoff | Assigned To | Florian Dold | ||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0010914: chunked upload by taler-harness? | ||||
| Description | When running tests and looking at the traffic with wireshark, I see that the taler-harness uses HTTP *chunked* uploads for the POSTed data, which is just insanely inefficient given that we're not streaming data. We should (1) check if this also happens by the production wallet (if so: priority up!), and (2) identify the cause (content-length not set early on?) and stop doing this. | ||||
| Tags | performance | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-01-25 15:04 | Christian Grothoff | New Issue | |
| 2026-01-25 15:04 | Christian Grothoff | Status | new => assigned |
| 2026-01-25 15:04 | Christian Grothoff | Assigned To | => Florian Dold |
| 2026-01-25 15:05 | Christian Grothoff | Severity | minor => tweak |
| 2026-01-25 15:05 | Christian Grothoff | Target Version | => post-1.0 |
| 2026-01-25 15:05 | Christian Grothoff | Tag Attached: performance |
