View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008768 | Taler | wallet-core | public | 2024-04-24 19:03 | 2024-05-06 22:18 |
| Reporter | sebasjm | Assigned To | Florian Dold | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Product Version | 0.11 | ||||
| Target Version | 0.11 | ||||
| Summary | 0008768: obs event: add a request handler to listen particular events | ||||
| Description | for example, if the user is waiting in the tx details view the only events shown will be the ones related to the actions taking into that screen (if the filter described in https://bugs.gnunet.org/view.php?id=8767 is implemented) the some activity in wallet core may be related to the current tx can take place (some tasks) to fix this, the UI should call this new request handler like: wallet.listenToTransactionTask(taskId) it will not return (may be cancelled by UI) and while this request is open all the ob events related to the `taskId` will be reported as related to this wallet request. with this we expect to ob even UI to show for example: database access or net request when the user is waiting in a withdrawal page or checking the purchase ticket (since it may have auto refund enabled) | ||||
| Tags | No tags attached. | ||||
|
|
We currently don't do subscriptions for wallet-core notifications. So I'm not sure how we would easily implement this. Maybe instead we can have a request to map a transaction ID to a list of task IDs (where the UI then filters relevant events for these tasks)? Sebastian, would that work? Alternatively we could indeed implement filtered notification subscriptions, but that would be a lot more complex. |
|
|
ok, if we have taskList = wallet.currentTasks(txId) and the we should keep that list updated, we will need an event to know when we should call it again and get an updated list. alternative, we can change this requirement to "there must be a way to get the Tx ID if the background operation is related to a transaction" for example: let's say that there is a cryptoStart event, if this comes from a withdrawal task... even if the withdrawal is not triggered by the current view (no wallet core operation has been called) the obs event must come with the txId so it can be filtered by the view. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-04-24 19:03 | sebasjm | New Issue | |
| 2024-04-24 19:03 | sebasjm | Status | new => assigned |
| 2024-04-24 19:03 | sebasjm | Assigned To | => Florian Dold |
| 2024-04-29 18:27 | Florian Dold | Note Added: 0022318 | |
| 2024-04-29 18:28 | Florian Dold | Assigned To | Florian Dold => sebasjm |
| 2024-04-29 18:28 | Florian Dold | Status | assigned => feedback |
| 2024-05-06 22:18 | sebasjm | Note Added: 0022362 | |
| 2024-05-06 22:18 | sebasjm | Assigned To | sebasjm => Florian Dold |
