Hi Daniel,
On 10/18/2011 12:22 PM, Daniel Wagner wrote:
Hi Jukka,
On 10/18/2011 10:24 AM, Jukka Rissanen wrote:
On 10/18/2011 10:51 AM, Daniel Wagner wrote:
On 10/18/2011 09:36 AM, Patrik Flykt wrote:
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.
I implicitly assumed that the application creates a session at startup
and keeps it alive during the life time of the application. The
application behavior you have described here is the one we have agreed
upon. Call Session.Connect() is only a hint that the application would
like to have a connection.
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.
Just to make this point clear, the UI design and behavior is not
something I have come up. This is what is currently in our products and
the I want to get this somehow working with ConnMan too. So bear with
me, that I am unable to change that part. My proposal to solve this
issues might be stupid, over engineered, over thought or over thingy
(add any over XXX you want here).
I understand and feel your pain :)
It would just be nice to keep API connman simple and now the session API
starts to look like that it is tailored to what one certain application
needs.
Having said that, let me explain what our UI does. At bootup of the
platform all application are started. All application register themself
at the main HMI application. They signal the HMI when an application is
available or not. The HMI will only display the application when the
application is pretty sure a connection is possible.
Another important thing to note is that the application tells the HMI
upfront why it is not ready (e.g. no network available, no connection
possible due to ongoing phone call (GSM limitation). So we want to have
some status/error messages. This is differs from the current smartphone
behavior where you start an application and get the error message
_after_ you have started the application. It is clear this is not 100%
fail safe.
Is it possible to know whether you can connect to certain bearer until
you call session.connect? If it is not possible, then the connect button
is quite useless.
I suggested the BearerAvailable Setting in order to have one part of
this puzzle solved, knowing when a connection has chances to be successful.
What is your thoughts on this?
cheers,
daniel
Cheers,
Jukka
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
