Currently, we allow up to 5 saved Wi-Fi networks. The data structure containing this information is stored in the chip's flash and is loaded on startup (see #7).
Anytime there is a change to the saved networks (add/remove/modify), the entire data structure is written back to flash. We should investigate how much wear this causes and whether or not it will be a problem in practice. If yes, we should look at other ways of maintaining the information (e.g., allow fragmentation and store is_free flags separate from the main data structure to enable smaller writes).
Also the list order doesn't really matter, which may help simplify the eventual implementation.
Currently, we allow up to 5 saved Wi-Fi networks. The data structure containing this information is stored in the chip's flash and is loaded on startup (see #7).
Anytime there is a change to the saved networks (add/remove/modify), the entire data structure is written back to flash. We should investigate how much wear this causes and whether or not it will be a problem in practice. If yes, we should look at other ways of maintaining the information (e.g., allow fragmentation and store
is_freeflags separate from the main data structure to enable smaller writes).Also the list order doesn't really matter, which may help simplify the eventual implementation.