-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block and Link Format support #18
Comments
I will add some features in the next few weeks. Can you tell me what would you do with Blockwise Transfer and Link Formats ? |
Hi, |
CoAP is a new protocol. Many libraries are still under the process. Can you talk about which one implement the most of features among your tested libraries ? |
Among the ones I've selected thus far, I'd say Californium (java), libcoap (c), libnyoci (c), txThings (python), CoAPthon (python), aiocoap (python), jcoap (java) and canopus (go) are fairly complete. Californium and libcoap are probably the most mature ones, I would guess. I'm still in the process of selecting other candidates, though. If you are interested, I've also found this paper [1] from 2017 which does a feature and performance comparison between some (a few) implementations. [1] https://www.sciencedirect.com/science/article/pii/S1877050917309870?via%3Dihub |
Thank you for your information. |
Maybe split this in two? I could use Block1 transfers for updating device firmwares, but have no need for the link format (atm). I'm sure other people have other priorities. Anyway, they are two different parts of the spec. and are separate features. |
@ea2973929 Of course. These two features have no relationship. I will do it later and any pr will be appreciate. |
Block1/2 is supported in this repo. |
Hello,
I know this library doesn't support Observe RFC yet. Does it support Blockwise Transfer (RFC7959) and Link Formats (RFC6690)?
Besides those, which other options are NOT supported?
Thanks!
The text was updated successfully, but these errors were encountered: