Currently, the network reconfiguration code contains a lot of long delays and retry mechanisms to make sure the networking subsystem (just wifi really) is done with whatever it was asked to do.
This introduces unnecessarily long delays and sometimes half/wrong information; which is all very bad for the user experience.
We might be able to improve this by using ubus, an event system openwrt uses. A lua binding exists, as well as a shell command.
More information: http://wiki.openwrt.org/doc/techref/ubus.
For instance to get wlan state information, run: ubus call network.interface.wlan status.
ubus also offers the possibility to talk to it directly using http/JSON. probably completely eliminating wifi/network connection things in the lua API (certain parts can be shielded with a login)
Currently, the network reconfiguration code contains a lot of long delays and retry mechanisms to make sure the networking subsystem (just wifi really) is done with whatever it was asked to do. This introduces unnecessarily long delays and sometimes half/wrong information; which is all very bad for the user experience.
We might be able to improve this by using ubus, an event system openwrt uses. A lua binding exists, as well as a shell command. More information: http://wiki.openwrt.org/doc/techref/ubus. For instance to get wlan state information, run:
ubus call network.interface.wlan status
.