bw-hro / webthing-cpp Goto Github PK

The /actions and /events endpoints must also response with Content-Type application/json and allow CORS

From all information available about the thing(s) an OpenAPI specification could be generated and hosted.
https://playground.thingweb.io/ offers something like that for WoT TD.

Some http clients automatically transform json request body like {"myDoubleProperty":123.0} to {"myDoubleProperty":123} which conforms to the json standard but makes type checking for C++ harder.

Webthing-CPP should support both input variants for double properties. At the moment it responds with 400 - value type not matching.

At the moment all emitted events as well as requested actions will be saved in memory. For long running applications with limited resources this could become a problem.

Possible attempts:

• limit number of actions/events that will be stored.
• limit duration how long to keep objects in memory (e.g. 1hour, 1day, 1week, ...)
• limit memory used e.g. 256MB

when limit is reached

• Oldest element will be removed to store new one. (like rolling appenders known from logging)
• removed objects could be persisted as backup. e.g. in a text file, sqlite db, ...

Console output of default logger could be colorful dependent on log level.

e.g. error: red, warn: yellow, info: white, debug: gray

make this configurable?

Add flavor option to generate interface that is compatible with WoT standard. This would allow to let the thing live in WoT ecosystem.

also cf.

• https://www.w3.org/TR/wot-thing-description
• https://playground.thingweb.io/
• http://plugfest.thingweb.io/webui/
• https://github.com/draggett/arena-webhub