martel-innovate / ewine-connectivity-manager Goto Github PK

As discussed, let's cleanup a bit the endpoints:

networks/ -> List of stored networks in /etc/networks/interfaces.
scan/ -> Scans available network, requires the interface name (e.g wlan0)

If you want, you can add the /interfaces.

Remember the PR for this one.

Simple pointers to:

• which python version will this support
• setup the requirements (virtualenv + requirements.txt)
  etc.

Can we add "preferences" to wifi networks? I.e, user prefers connecting to network2 even if it has lower signal than network1 (also available).

As discussed :)

I can't recall exactly if we talked about this, but I'm putting this down so as not to forget.

Todo: Let's remove those "db"-prefixed endpoints from the API. If the configuration can be persisted in a file or in a database, that's an implementation detail. Implementation details should not leak in the APIs. Why would the api user care where the info is stored?. The decision of wether to use a file, db or both could be made at the init time of the service.

Same applies to the reference to "file" or "database" from the "purpose" documentation.