|
|
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | |
|---|
| Priority | high | Severity | major | Reproducibility | have not tried |
|---|
| Status | closed | Resolution | fixed | |
|---|
| Product Version | Git master | |
|---|
| Target Version | 0.9.3 | Fixed in Version | 0.9.3 | |
|---|
|
|
| Summary | 0002277: DHT PUT continuation should only be called after confirmation from service |
|---|
| Description | After recent (SVN 21019) changes (in conjunction with fixing 0002274) the lack of a confirmation for a DHT PUT from the DHT service is problematic. Already before, a client could never be sure that a PUT was actually received by the service. Thus we should change the IPC protocol to force the DHT service to send a confirmation and to wait in the DHT API for that confirmation (or timeout). This change should have no impact on the outside API (we might want to change the signature of the continuation to better report the result of the operation, but that's almost orthogonal). |
|---|
| Steps To Reproduce | The command-line tool 'gnunet-dht-put' might now terminate before actually sending the PUT to the service. This 'error' is likely non-deterministic (I have not tried this, but as the 'finish write on disconnect' is gone, this should be an implication of the current design). Real-world usage should not be directly aversely affected (as they keep the client-service connection open longer). |
|---|
| Tags | No tags attached. |
|---|
|
|
