On 11/11/2019 14:43, Gladish, Jacob wrote:
Yes, I totally agree. I'd like to do something like you're suggesting but without having a fork or use a heavily patched version of hostapd.
I'm sure there are people out there that are interacting on that socket with their own applications. For backwards compatibility, it would make more sense to create yet another socket interface that does what you're suggesting and give people a few versions to move off that onto the newer interface.
I'm one of these people. libdhcpcd (part of dhcpcd-ui) communicates with
wpa_supplicant over the socket interface.
I don't have any real issue with the current interface.
Have you considered that dealing with strings is entirely language
agnostic though? Changing to C style structures and using flags to
interpret numbers may cause issues for other tools that may want to
communicate. If this ever wants to work over a wire this also creates
more issues such as alignment, padding, endianness and bit size. None of
which are a problem for human readable strings.
When writing libdhcpcd, one of the design considerations was how dhcpcd
would communicate. I took a similar approach as here - dumped the shell
variables to the listener socket and let the client work it out. No need
to create a second way of doing things just for a socket vs a shell
script. Yes it's more work at the client side, but it keeps the
important side, the host side, simple.
Roy
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
