Hacker News Reader

Comment by johnlbevan2 | Hacker News Reader

For those unfamiliar with CoAP, it's a REST based protocol for machine-to-machine communication targeted at IoT (Internet of Things) scenarios particularly in Home Automation.

NB: Unlike REST though, URLS begin COAP:// instead of HTTP:// or HTTPS://.

This site gives a good overview: https://www.slideshare.net/jvermillard/co-ap Whilst this gives a lot more info: http://coap.technology/

View on HN

Also, the RFC is quite a nice read: https://tools.ietf.org/html/rfc7252

I particularly like the introduction, which succinctly explains the value in realizing a subset of REST common with HTTP, while not just blindly trying to make a compressed version of HTTP. The end result is a protocol which is quite easy to map to each other, not just in terms of implementation but also in terms of mindset. Being familiar with HTTP means you won't feel completely lost in trying to learn CoAP, which is pretty cool.

This is great. Thanks for the link! Its well written and shows great clarity of thought. The practical considerations are always mentioned, and they thought of everything, even ddos amplification attacks. A thing of beauty.

s/Unlike REST/Unlike HTTP

I think your regular expression needs a /g at the end, no?

Edit: This was a serious question, not sure I deserve multiple downvotes

It only needs "/". "g" finds all matches, but there is only one match in the string.

Still needs the trailing /

Only for sed/perl. Not if you are using vim (although in that case it's missing the leading `:`).

Reply on news.ycombinator.com