On 12/31/2013 05:38 PM, Pozdnyakov, Mikhail wrote:
Hi Shawn,

I'd prefer extension option (option #1) because of application API permissions 
control (we can load or not load an extension depending on the app permissions).
And it is not quite clear for me how we can handle it with option #2. Maybe 
Ming Bai has some idea on that since he is implementing application permissions 
subsystem.
Thanks pointing this out. Currently the permission system is consist of two major parts: the "API permission check" which is bound to the extension framework for doing runtime permission check, and the SMACK -- for the process-level permission control. So if we bypass the extension framework, we would bypass one of the major permission check mechanism and will lose some important features.

On other hand performance is also very important. Is there any way to make 
extension approach perform better?

BR,
Mikhail

________________________________________
From: Crosswalk-dev [[email protected]] on 
behalf of Gao, Shawn [[email protected]]
Sent: Friday, December 27, 2013 1:29 PM
To: [email protected]
Subject: [Crosswalk-dev] The ways to implement native file system api

Hi, All,
I am working on Native File System Api. See feature description on Jira, 
https://crosswalk-project.org/jira/browse/XWALK-672 .
There are two options to implement this feature.
1. Take currently crosswalk extension framework to implement native file system 
api. Like Contacts and Messaging api.
         * The pros, only js and java programming required. Don’t touch any 
Blink or Chrome code.
         * The cons, It gets 2 times slower than option2, Because of base64 
encode/decode operation in each js and java side.
2. Modify code in Blink and Chrome to extend the ability of requestFileSystem() 
to access native file system.
         * The pros, faster and straightforward for web developer. Reuse the 
code for objects like “FileEntry”, etc.
         * The cons, Modify Blink and Chrome code may get more risk. Maybe 
cannot be accepted by upstream.

Any suggestions are appreciated.

Thanks,
Shawn

---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

Reply via email to