Hi Marcel, On 10/18/2011 05:18 PM, Marcel Holtmann wrote: >>> So we have 99% of application that should only be notified when they are >>> really online. Telling them that we are ready, but not online, just >>> wakes them up for no real reason. >> >> I am 67,6% sure your numbers are not correct. >> >>> The only 1% that might care about link local connections are the DLNA >>> type of application for your home entertainment. Similar to what Apple >>> does with AirPlay. However we already have Avahi for this stuff. Why >>> would we need another set of notifications? >> >> Okay, let's leave the "connecting" state away, what about the "suspend" >> one? Would you prefer to model it as new Setting instead of merging this >> one into Online? > > Lets think about application wakeups first. Why do you wanna wake up an > application for this. I do not see the need for it.
The application is already running (or in a running state) in this scenario. > To be honest this all sounds fine on the surface, but once I look at the > implications I am having problems to come up with a good reason on doing > this. I am currently not seeing this need. If an application knows that the data link is suspended it could stop all timeout timers because it doesn't make sense to keep them running. If the link resumes the timer can also be resumed. This is what I have heard is working quite good for our current implementation here and hence the request to have something similar around. I see that oFono exports this information through the Suspended property in the ConnectionManager API. I didn't see anything like this on the BlueZ APIs (when ConnMan uses PAN). So this information is already there and can be used at least for real modems. I don't really understand your argument about the implications. cheers, daniel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
