Hi all,

I've took a look at the code and it looks great to me.

However winet-service register a connman's agent directly through dBus instead of using the related function available in connman-lib. Its seems more logical to me to call the connman-lib from winet-service to limit dBus calls only to connman-lib.

Is this current status only temporary ? Or maybe there's a reason to rely on this current architecture ?

BR,

Stephen

On 03/07/2014 04:32, Xu, Martin wrote:

+ Steve

According to our plan at Comms F2F meeting ,We have finished the first stage work to deliver WiNet High Level Design, Prototype and Benchmark. we also shared the prototype code on Tizen.org.

I'd like to get feedback from all the Tizen community, which is very valuable for us. According to the feedback, we will finalize the design and release WiNet 0.1, and then, the new features will added step by step.

Thanks!

*From:*Zhang, Zhengguang
*Sent:* Wednesday, July 02, 2014 19:23
*To:* '[email protected]'
*Cc:* '[email protected]'; 'C S BHARGAVA'; '[email protected]'; 'PRADEEPKUMAR BELLARY'; Le Foll, Dominique; Liu, Bingwei; Zhu, Peter J; Xu, Martin; '[email protected]'; '[email protected]' *Subject:* RE: Tizen WiNet (WiFi & Network) Framework Prototype Version is Released!

Hi, All

We tested the WiNet framework prototype version on our Mobile platform, and below are some memory consumption data comparing with the current Tizen solution:

Opertions

        

Current Tizen Solution

        

WiNet Framework Solution

        

Improved Percent

WiFi Enabled

        

net-config: ~840K

        

winet-service: ~520K

        

(840-520)/840 = 38%

WiFi Connected

        

net-config: ~850K

        

winet-service: ~530K

        

(850-530)/850 = 38%

WiFi Tethering Enabled

        

net-config: ~840K

mobileap-agent: ~1230K

        

winet-service: ~520K

        

(840+1230-520)/(840+1230) = 75%

From the prototype data, we can see WiNet framework solution can save much more memory than current tizen solution from middle layer.

We will continue to optimize and implement it, and any suggestions during your review process, don't hesitate to let me know please.

Thanks,

Zhang Zhengguang

*From:*Zhang, Zhengguang
*Sent:* Friday, June 27, 2014 10:20 AM
*To:* [email protected] <mailto:[email protected]>
*Cc:* '[email protected]'; 'C S BHARGAVA'; '[email protected]'; PRADEEPKUMAR BELLARY; Le Foll, Dominique; Liu, Bingwei; Zhu, Peter J; Xu, Martin; [email protected] <mailto:[email protected]>; [email protected] <mailto:[email protected]> *Subject:* Tizen WiNet (WiFi & Network) Framework Prototype Version is Released!

Hi, All

Tizen WiNet(WiFi & Network) Framework prototype version is released, now it can support the basic functionality of Tethering and WiFi Station features, we will continue to optimize and implement it. When it can support the total feature of Tethering and WiFi station stably, we will release 0.1 version formally, also we plan to combine WiFi P2P and hotspot 2.0 features in the framework in future.

Attachment is a simple slide to introduce what WiNet framework is and what it aims to do, you can refer to it for details.

WiNet framework includes 3 layers: ConnMan Lib, WiNet Service Daemon and CAPI layer, and the source code have been submitted to tizen.org, you can get them from the locations below:

1). ConnMan-lib

Platform/core/connectivity/connman-lib (tizen_devel branch)

2). WiNet Service Daemon

Platform/core/connectivity/winet-service      (tizen_devel branch)

3). CAPI layer

In the first phrase, we keep all the related CAPI packages and interfaces unchanged, so you can get it from the old packages:

Platform/core/api/wifi (tizen_devel branch, for WIFI station CAPI support)

Platform/core/capi/tethering (tizen_devel branch, for tethering CAPI support)

There is a test program for every layer of the framework, so you can test every layer by installing the related test program in your device.

Also you can review the source code and give your proposal freely, any suggestions, feel free to let me know, thanks!

Regards,

Zhang Zhengguang



_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to