Allow for config of SN_COAP_DUPLICATION_MAX_MSGS_COUNT using yotta config about mbed-client-c HOT 9 CLOSED

Hi, Can you please elaborate on your use case ? What are you trying to achieve here ? This configuration is not enabled on yotta level yet because we didn't have the use case yet so even if we provide enabling this config, we would need to test this case.

from mbed-client-c.

At the moment, it seems the stack by default is not filtering duplicate CoAP packets out. At least we've seen duplicate messages with the same ID being delivered to the application, resulting toggle actions being acted upon twice.
We assume that the stack would do the filtering when defining SN_COAP_DUPLICATION_MAX_MSGS_COUNT non zero. Would be good to be able to yotta config it, since it has an impact on RAM/ROM size, or?

from mbed-client-c.

Yes, currently there is no yotta config for this, we can add this parameter in mbed-client-c. We will update this issue when we add this feature flag .

from mbed-client-c.

ARM Internal Ref: IOTCLT-621

from mbed-client-c.

Update: this is planned for the next sprint. If everything goes well, it will be released after that.

from mbed-client-c.

When does the sprint start? How long are your sprints?

Markus

From: Marcelo Salazar [mailto:[email protected]]
Sent: Mittwoch, 23. März 2016 10:40
To: ARMmbed/mbed-client-c [email protected]
Cc: Becker Markus [email protected]
Subject: Re: [mbed-client-c] Allow for config of SN_COAP_DUPLICATION_MAX_MSGS_COUNT using yotta config (#31)

Update: this is planned for the next sprint. If everything goes well, it will be released after that.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-200270385

________________________________________________________ The contents of this e-mail and any attachments are confidential to the intended recipient. They may not be disclosed to or used by or copied in any way by anyone other than the intended recipient. If this e-mail is received in error, please immediately notify the sender and delete the e-mail and attached documents. Please note that neither the sender nor the sender's company accept any responsibility for viruses and it is your responsibility to scan or otherwise check this e-mail and any attachments.

from mbed-client-c.

Hi,
We will start working on this next week and this shouldn't be a big task to complete. I'll update this issue once the change is published, should be ready by the end of the next week.

from mbed-client-c.

Hi Markus,

There is now version that allows to change duplication message count via yotta configuration system. It's released in mbed-client-c version 2.3.2.

To enable message duplication, you need to create a config.json file in the application level.
An example:
{
"coap_duplication_max_msgs_count": 1
}

Please, let us know if this solves your original issue.

from mbed-client-c.

Great. Thanks.

from mbed-client-c.