Design Notes

• Use Iron?
  • Node style webserver, has a lot of middleware available. Long term this is probably going to be better than rustful which isn't so extensible
• Travis (Linux), Appveyor (Windows)
• Cross compile to rpi, what do we need to achieve this?
• Core API features
  • Devices
    • Schema
    • Proxy
      • Must support device pushing event to server (and server further pushing event to clients)
  • Users
    • Authentication
    • Authorization
  • Data storage
    • We want some way to store and retrieve historical data. Do we just expose an endpoint for clients to create new tables and push data into it as they see fit? i.e. a remote script access the API, subscribes to device events and then stores them in the data storage.
  • Alternatively, we could store historical responses from devices. So the clients can always fetch the entire state of a device in the past. Assuming a reading a minute each 1KB in size that's just 1.44MB per device per day!