View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001933 | GNUnet | obsolete | public | 2011-11-22 18:54 | 2024-05-03 12:02 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | Due Date | |
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Product Version | Git master | ||||
| Target Version | 0.9.4 | Fixed in Version | 0.9.4 | ||
| Summary | 0001933: peerinfo notifications on expiration | ||||
| Description | It is not clear if peerinfo triggers all (necessary?) notifications whenever addresses expire. Or we should change the API to explicitly state that such notifications will not happen. But then we'd need to notify if expirations are updated (increased). Either way, notifications on expiration need a bit of work. | ||||
| Tags | No tags attached. | ||||
| Peerinfo code *does* notify clients if expiration times go up. So now clients only need track that addresses expire, but that they can do internally just as well without notifications; this should be about as efficient as pushing notifications out, so this issue can be closed. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-11-22 18:54 | Christian Grothoff | New Issue | |
| 2011-11-22 19:16 | Christian Grothoff | Priority | normal => low |
| 2011-11-22 19:16 | Christian Grothoff | Status | new => confirmed |
| 2012-02-21 20:55 | Christian Grothoff | Target Version | => 0.9.4 |
| 2012-05-02 23:17 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2012-05-02 23:17 | Christian Grothoff | Status | confirmed => assigned |
| 2012-06-02 23:21 | Christian Grothoff | Priority | low => high |
| 2012-06-13 14:52 | Christian Grothoff | Note Added: 0006063 | |
| 2012-06-13 14:53 | Christian Grothoff | Status | assigned => closed |
| 2012-06-13 14:53 | Christian Grothoff | Fixed in Version | => 0.9.4 |
| 2024-05-03 12:02 | Christian Grothoff | Category | peerinfo service => obsolete |