Your service daemon will do that right? We can't proxy all the call from the WiNet daemon.
That has been talked and decided after long time discussion. From: Dominig ar Foll (Intel OTC) [mailto:[email protected]] Sent: Thursday, July 24, 2014 13:37 To: Xu, Martin; [email protected] Subject: Re: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is Released! Martin, I want the call to pass via the Deamon, not to see lib linked to the calling app to call directly BlueZ. Dominig ar Foll Senior Architect Intel Open Source Technology Centre Le 24/07/2014 21:01, Xu, Martin a écrit : According to our design, all the ConnMan feature should go through WiNet from CAPI. So at Tizen, the up layer interface is CAPI not ConnMan API, that is the design. That is what you want? If Stephen find any code break the concept, any patches are welcome. From: Dominig ar Foll (Intel OTC) [mailto:[email protected]] Sent: Thursday, July 24, 2014 11:46 To: Xu, Martin; [email protected]<mailto:[email protected]> Subject: Re: [Dev] Tizen WiNet (WiFi & Network) Framework Prototype Version is Released! Le 24/07/2014 20:01, Xu, Martin a écrit : Ok then, as we discussed before should be done at service daemon layer, right? And WiNet just provide the CAPI? Yes. But for that the change indicated by Stephen must be implemented. Dominig
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
