Background
To this date, the remote-control-lab API is quite messy. It consists on passing variables inside jsons, that will change depending on the opened uri of the Websocket.
The json-coded variables don't seem off, but the idea of the communication behaving differently for each uri does ring a bell. This data-flow should be, ideally, uniform.
Before firing with ideas, lets set the boundaries.
Requirements
- A lighweight communication protocol. (must fit in ESP8266)
- A scalable protocol. (Needs to work almost without modifications for other subsystems)
- Ultra Low latency for sensor-actuator stuff. (how low? whats the control system limit?)
- Normal latency for configuration and set-up.
- Reliability for configuration messages.
- Some reliability for high frequency messaging (like actuator-sensor stuff)
Nice to have
- ReSTful.
- Standard.
- Testable.
What needs to be done
Do the necessary research to define an API that fulfills every requirement, or the closest one.
Write a POC.
Background
To this date, the remote-control-lab API is quite messy. It consists on passing variables inside
jsons, that will change depending on the openeduriof the Websocket.The json-coded variables don't seem off, but the idea of the communication behaving differently for each
uridoes ring a bell. This data-flow should be, ideally, uniform.Before firing with ideas, lets set the boundaries.
Requirements
Nice to have
What needs to be done
Do the necessary research to define an API that fulfills every requirement, or the closest one.
Write a POC.