View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008310 | Taler | libeufin-nexus | public | 2024-02-02 19:49 | 2024-02-02 19:49 |
| Reporter | Christian Grothoff | Assigned To | Antoine A | ||
| Priority | normal | Severity | text | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0008310: does ebics-submit support DB notification? | ||||
| Description | The nexus-manual currently suggests that the "ebics-submit" subcommand can be run either at a fixed frequency, or manually (one-shot). What I expected is that by now we also support (or even default to) some "LISTEN" mode where we subscribe to database events (basically, NOTIFYs done whenever a new transaction is INSERTed into the table where outgoing payments are queued) and then the ebics-submit job would wake up immediately whenever the notification comes in. We may additionally have a FREQUENCY option to limit EBICS submissions (say at most once per 5 minutes, unless there are too many active transactions, etc.). But overall, there should be a "basically instant" mode based on DB notifications and not just on timeouts. If the documentation is wrong on this, then this might be just a documentation issue. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-02-02 19:49 | Christian Grothoff | New Issue | |
| 2024-02-02 19:49 | Christian Grothoff | Status | new => assigned |
| 2024-02-02 19:49 | Christian Grothoff | Assigned To | => Antoine A |
