Hi Patrik, On 31.01.2012 08:35, Patrik Flykt wrote: > On Mon, 2012-01-30 at 13:20 +0100, Daniel Wagner wrote: >> My argument here is that if we start to optimize on this level >> (message size) we need some real numbers first. For example, how much >> do 50 extra bytes hurt? > > The message size is not that relevant for a few numbers of apps. When > the amount of apps starts to increase, we're in for more pressure > removing this redundant info. But meanwhile, app and UI writers have > learned to ignore the meaning of State, since they think ConnMan will > babysit for them and tell the state for each and every property. And > then we have a problem.
Is the main argument about the API we have that the UI devs should not have to think to much? If you look at the PropertyChanged messages, an UI just does once GetProperties() and then listens for the PropertyChanged messages. The Notifcation API is designed exactly the same way. So your proposal changes this. For me that is not a problem but I just want to highlight that we introduce a different behavior pattern here. cheers, daniel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
