Hello, Have you considered implementing this as an extension in C++? I suspect you are getting some extra overhead to go from C++ to Java and come back, and it doesn't seem to me we need any Java specific API do reach the file system (guessing here).
I suggest you take route #1 for the reasons Mikhail and Thiago already pointed: for integrating with the permission system in Crosswalk (that wouldn't be available to Blink/Chrome code, so we would have to add tweaks to control this specific permission there) and because we do have some room for improvement on extension system itself. Cheers, Caio From: Crosswalk-dev [mailto:[email protected]] On Behalf Of Gao, Shawn Sent: Friday, December 27, 2013 9:30 AM 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
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
