Repository navigation
Conversation
fa939b1 to
0af8db6
Compare
4becf0b to
0272b27
Compare
d8e717b to
fb7a4aa
Compare
3dabb24 to
4b60a6b
Compare
7bc46d1 to
db5b584
Compare
|
It would be good if a server side API could be added where the calling application can define the CID to use so that it can be tracked by the application to change the tuple to send back any response on. |
As for now, tinydtls CID only supports the client side. To be more precise, the client only indicates to support CID, but doesn't use a CID on it's own side. For the next time I will not able to spend the required time to implement a server side. If that changes, the proposed API will make a lot of sense. |
Simple client side implementation indicates support and uses the cid of the server, when negotiated by that. Signed-off-by: Achim Kraus <achim.kraus@cloudcoap.net>
Signed-off-by: Achim Kraus <achim.kraus@cloudcoap.net>
|
@boaks Any chance of getting this (or equivalent) merged into main? |
|
If I remember it well, we want to try to get the most other PRs merged before adding CID. |
|
Should we change that approach? The we may convert the feature branch into a PR. |
|
There is no harm in having a feature branch being a PR for main at the same time. So, if there is demand for CID, just go ahead opening a PR. |
Just done this with #302. |
Simple client side implementation indicates support and uses the cid of
the server, when negotiated by that.
Signed-off-by: Achim Kraus achim.kraus@cloudcoap.net