2 ms·
Google WiFi had a local API for config and status etc. But it appeared to be single threaded and some API calls took 30s+, while all others queued up behind.
by londons_explore 4y ago
Google WiFi had a local API for config and status etc. But it appeared to be single threaded and some API calls took 30s+, while all others queued up behind.
Nobody can build a nice app based on such an API. The official app tried - there were spinners on every part of the UI. Even simple things like 'give me a graph of network bandwidth' would have gaps in the graph where the single threaded service was bogged down with other requests.