Closed sbernard31 closed 1 year ago
There is release v6.12.0 that contains implementation for this ticket, can we close it?
I tested it and it works, but I have to admit that I didn't look into it enough when I ask for it at https://github.com/open-coap/java-coap/issues/27#issuecomment-1513155898 :
Because, I was thinking that :
coapServerBuilder.retransmission(RetransmissionBackOff.ofExponential(Duration.ofMillis(200), 4, 1));
will send re-transmission each 200 ms (linear) but it is rather 200ms, then 400ms, then 800ms (exponential)...
So to be clearer :
So we can close this issue :slightly_smiling_face: Thx :pray: and sorry for the confusion.
Some feedback/questions not really related to this :
responseTimeout
which is a good idea, but I understand (not totally sure) that it is not optional ? (maybe both question deserve their own issue?)
- I see there is a
responseTimeout
which is a good idea, but I understand (not totally sure) that it is not optional ?
There has to be some timeout, it could be big one if needed.
- Not the first time when I update java-coap there is API break between 2 minor version, for now this is not a problem as we are in development phase, but if we release a stable version of Leshan including java-coap dependency, that could be an issue. Did you already consider to maybe move to Semantic Versioning ?
Yes, I am aware of that. When needed, we can switch to be more strict with API changes.
(maybe both question deserve their own issue?)
Yes :)
Currently we can only set
ACK_TIMEOUT
andMAX_RETRANSMIT
but notACK_RANDOM_FACTOR
.This issue was triggered by : https://github.com/open-coap/java-coap/issues/27#issuecomment-1513155898