View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002116 | GNUnet | util library | public | 2012-01-26 14:31 | 2012-02-28 10:05 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | Due Date | |
| Priority | urgent | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.9.0 | ||||
| Target Version | 0.9.2 | Fixed in Version | 0.9.2 | ||
| Summary | 0002116: resolver sends 'struct sockaddr'(in/in6) in IPC protocol | ||||
| Description | This is not really portable (how to write Java client that works on systems with different struct sockaddr's?). Also, why send the port like that? Overall, the resolver protocol clearly needs to be cleaned up. | ||||
| Tags | No tags attached. | ||||
| Resolver API now appends 'struct in_addr' (4 bytes) or 'struct in6_addr' (16 bytes) depending on AF_INET or AF_INET6 being set (or of course still the 0-terminated hostname for normal lookups). The replies were changed in the same way. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-01-26 14:31 | Christian Grothoff | New Issue | |
| 2012-01-26 14:31 | Christian Grothoff | Status | new => assigned |
| 2012-01-26 14:31 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2012-01-27 12:48 | Christian Grothoff | Note Added: 0005395 | |
| 2012-01-27 12:48 | Christian Grothoff | Status | assigned => resolved |
| 2012-01-27 12:48 | Christian Grothoff | Fixed in Version | => 0.9.2 |
| 2012-01-27 12:48 | Christian Grothoff | Resolution | open => fixed |
| 2012-02-28 10:05 | Christian Grothoff | Status | resolved => closed |