Hi Daniel,
On 10/18/2011 10:51 AM, Daniel Wagner wrote:
On 10/18/2011 09:36 AM, Patrik Flykt wrote:
Hi,
On Thu, 2011-10-13 at 08:04 -0700, Daniel Wagner wrote:
+ boolean BearerAvailable [readonly]
+
+ As soon as a matching bearer is available
+ BearerAvailable will be set to True.
This has the side effect of waking up applications whenever a matching
bearer/technology is nearby and get worse battery/power behavior. IMHO
this attribute might not really be that useful.
This would help in the case where we want to gray out the connect button
in the UI when no service available.
When application (in this case UI) wants a connection it creates a
session. The session is then connected when certain/any bearer is
available. If the is no bearer available then no connection is created.
Why would there be a button for monitoring bearer availability?
Would it be better to let connman do the connecting automagically, why
there is need to have a manual connection activation (user interaction).
So the UI would just say that user wants to connect automagically to
these bearers and connman would just then create connections when the
bearers are available.
If the Session API doesn't have this information, where do I get it
from? Should I start enumerate all Services and trying to figure out in
which Service has been selected by the session code?
cheers,
daniel
Cheers,
Jukka
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
