View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001745 | GNUnet | core service | public | 2011-08-04 11:45 | 2011-10-31 12:00 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Product Version | Git master | ||||
| Summary | 0001745: core does not process message type map messages yet | ||||
| Description | core now generates message type maps, but the code does not use them yet (there is a FIXME in the code). The idea behind message type maps is that we ONLY tell clients about connected neighbours IF those neighbours have registered for an overlapping set of message types. However, if a client registers for no message types at all, that client should be notified about all neighbours. What we still need to implement is to store with each neighbour record the associated message type map. Then, if we receive a message from a peer that is not in its message type map, we should add the respective type (as a back-up for the case that a message type map is dropped). Similarly, if we receive an updated type map, we need to update the neighbours map. In both cases, whenever bits are added/removed from a neighbours MTM, we need to re-compute the intersection with the message types sets for all clients and notify the respective clients (connect/disconnect events). Finally, for new clients and/or connections, we need to also consider the message type maps before generating connect/disconnect notifications. And then testcases will need to be checked to make sure that they still pass with the new notification rules. This will enable GNUnet to NICELY run with different applications/services above core, all of which typically assume that all other peers run the same set of services/applications. | ||||
| Tags | No tags attached. | ||||
| related to | 0001815 | closed | Christian Grothoff | core sends NotifyTraffic message (NOTIFY_INBOUND) for peer that is not connected |
|
|
This is now implemented in gnunet-service-core-new, which after some more testing will replace the old gnunet-service-core. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-08-04 11:45 | root | New Issue | |
| 2011-09-16 10:37 | Christian Grothoff | Reporter | root => Christian Grothoff |
| 2011-09-16 10:37 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2011-09-16 10:37 | Christian Grothoff | Status | new => confirmed |
| 2011-09-16 10:37 | Christian Grothoff | Product Version | => Git master |
| 2011-09-16 10:37 | Christian Grothoff | Target Version | => 0.9.0 |
| 2011-09-19 10:12 | Christian Grothoff | Target Version | 0.9.0 => 0.9.0pre4 |
| 2011-09-19 11:50 | Christian Grothoff | Priority | normal => high |
| 2011-09-19 11:56 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2011-09-19 11:56 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2011-09-19 11:56 | Christian Grothoff | Status | confirmed => assigned |
| 2011-10-07 13:29 | Christian Grothoff | Relationship added | related to 0001815 |
| 2011-10-11 14:58 | Christian Grothoff | Note Added: 0004701 | |
| 2011-10-11 14:58 | Christian Grothoff | Status | assigned => resolved |
| 2011-10-11 14:58 | Christian Grothoff | Fixed in Version | => 0.9.0pre4 |
| 2011-10-11 14:58 | Christian Grothoff | Resolution | open => fixed |
| 2011-10-31 12:00 | Christian Grothoff | Status | resolved => closed |
