Wanting to turn the Ploggs, into more RESTful devices, I needed to add a web server (HTTP) to the C++ code managing the Ploggs. After comparing and trying a number of lightweight web servers (Apache was not an option for this kind of small app) I picked SHTTPD, mainly because: It was one of the few I managed to embed in my C++ code (I’m not a C expert…) It offered the possibility of registering call back methods when a particular URL is called, which makes it a quite good candidate for a REST interface. Here is how I did...
Super excited to announce that @EVRYTHNG now supports one of the most disruptive tech I've seen in the #IoT: @WiliotHQ battery-free low-cost #Bluetooth tags. evrythng.com/wiliot-and-evr… #DigitalLink #batteryFree #ble
Probably a good time for a shameless plug to remind everyone that the @EVRYTHNG platform fully supports using and managing large scale #physicalWeb #beacons deployments here is to how: developers.evrythng.com/docs/… #iot #smartTags @phwassoc
With HTTP/2 being rolled out it is time to think about HTTP/3 and there is good news for the #IoT and the #WebofThings: it is based on UDP and hence more lightweight and a better fit for a number of IoT use cases. nordicapis.com/what-is-coming… @webofthings pic.twitter.com/1RNmchixJl
Okay, our WoT device for Chapter 2 is now fully back up and running and so is the camera, enjoy! For the records the issue was an SD card fault. As said in the book, do not use SD cards in production! :D #webofthings @wotbook @ManningBooks pic.twitter.com/3wNPq0ZmOR