dbus is far too heavy for small embedded environments with fixed hardware. (even if you mean nothing else, it's about 500K too big). ubus was written for this environment to handle what dbus should not - and is very small (a few K). For even tighter systems, either skip entirely or roll one's own. I suggested OpenWRT's ubus infrastructure based on it already being widely in use on small architectures as well as being supported and maintained. hostap project handles a very wide range of hardware, including devices with very tight storage requirements. I suppose if you could find a good argument to get it <10K total in impact, tight, reliable, and with no side effects, that might be another story. (ubus isn't quite free of side effects, but its issues are very consistent and well known) Sorry to others for the noise. On Thu, 31 Oct 2019 at 13:30, Andrej Shadura <andrew@xxxxxxxxxx> wrote: > > Hi, > > On Thu, 31 Oct 2019 at 19:08, Teunis Peters <teunis.peters@xxxxxx> wrote: > > dbus has no business on embedded environments like AP > > it will not happen now, it may not ever happen. > > This is not true, I’ve seen and developed embedded systems with D-Bus. > > -- > Cheers, > Andrej _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
