Hi Patrik,

On 21.12.2012 14:41, [email protected] wrote:
From: Patrik Flykt <[email protected]>

Instead of using the session specific service entry, use the information
from the default service. The default service and the session specific
service entry point to the same service.
---
  src/session.c |   18 +++++++-----------
  1 file changed, 7 insertions(+), 11 deletions(-)

diff --git a/src/session.c b/src/session.c
index 30f833e..b38e7f7 100644
--- a/src/session.c
+++ b/src/session.c
@@ -647,17 +647,13 @@ static void append_notify(DBusMessageIter *dict,

        if (session->append_all == TRUE ||
                        info->entry != info_last->entry) {
-               if (info->entry == NULL) {
-                       name = "";
-                       ifname = "";
-                       service = NULL;
-                       bearer = "";
-               } else {
-                       name = info->entry->name;
-                       ifname = info->entry->ifname;
-                       service = info->entry->service;
-                       bearer = info->entry->bearer;
-               }
+
+               service = __connman_service_get_default();
+               ifname = connman_service_get_interface(service);
+               bearer = service2bearer(connman_service_get_type(service));
+               name = __connman_service_get_name(service);
+
+               DBG("append service %p", service);

Hmm, I am not completely sure if this is right direction. Basically this means all sessions will only use one service when this available. For my use cases I really need to have independent sessions, that means session 'a' uses the customers phone via Bluetooth where as session 'b' uses the built in modem.

thanks,
daniel
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman

Reply via email to