<commit_before>cantcoap
========

CoAP implementation that focuses on simplicity by offering a minimal set of functions and straightforward interface.

This is a CoAP implementation with a focus on simplicity. The library only provides PDU construction and de-construction.
The user is expected to deal with retransmissions, timeouts, and message ID matching themselves. This isn’t as arduous as it sounds and makes a lot more sense on a constrained device.
Imagine for example a simple microcontroller sensor that only reports readings once every 15 minutes, and only sends a few packets each time. Do you really need a complicated framework to deal with acknowledgements and re-transmissions?

Since CoAP recommends you only send one packet at at time, this means you only need to keep track of one on-going transaction at a time. I think you’re capable of doing the retransmission logic in a few lines of code.

Furthermore, the timers and interrupt processes between different embedded processor architectures, vary quite a bit. So it often makes sense to write the packet sending processes yourself.

Finally, you might be sending the packets over odd transport bearers such as a SMS or a simple radio bearer. In which case, it’s easiest to deal with buffers. If I built retransmission handlers, they’d all be UDP/IP specific and would bloat the code.
<commit_msg>Testing something with readme<commit_after>cantcoap
========

CoAP implementation that focuses on simplicity by offering a minimal set of functions and straightforward interface.

Compilation
-----------

Dependencies:

* CUnit 
	This is a testing framework for c. 

Just type make

Long description
----------------

This is a CoAP implementation with a focus on simplicity. The library only provides PDU construction and de-construction.
The user is expected to deal with retransmissions, timeouts, and message ID matching themselves. This isn’t as arduous as it sounds and makes a lot more sense on a constrained device.
Imagine for example a simple microcontroller sensor that only reports readings once every 15 minutes, and only sends a few packets each time. Do you really need a complicated framework to deal with acknowledgements and re-transmissions?

Since CoAP recommends you only send one packet at at time, this means you only need to keep track of one on-going transaction at a time. I think you’re capable of doing the retransmission logic in a few lines of code.

Furthermore, the timers and interrupt processes between different embedded processor architectures, vary quite a bit. So it often makes sense to write the packet sending processes yourself.

Finally, you might be sending the packets over odd transport bearers such as a SMS or a simple radio bearer. In which case, it’s easiest to deal with buffers. If I built retransmission handlers, they’d all be UDP/IP specific and would bloat the code.

{'fraction_non_alphanumeric': 0.03941908713692946, 'fraction_numerical': 0.0013831258644536654, 'mean_word_length': 4.43796992481203, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2692765', 'n_tokens_mistral': 676, 'n_tokens_neox': 638, 'n_words': 446}