`grep -r std::fs components` returns many results:
components/net/hosts.rs:use std::fs::File;
components/net/filemanager_thread.rs:use std::fs::File;
components/net/resource_thread.rs:use std::fs::File;
components/net/image_cache.rs:use std::fs::File;
components/net/fetch/methods.rs:use std::fs::File;
components/net/chrome_loader.rs:use std::fs::canonicalize;
components/config/resource_files.rs:use std::fs::File;
components/config/opts.rs:use std::fs::{self, File};
components/config/prefs.rs:use std::fs::File;
components/layout/layout_debug.rs:use std::fs::File;
components/style/build_gecko.rs: use std::fs::{self, File};
components/style/build_gecko.rs: use std::fs;
components/script/build.rs:use std::fs::File;
components/script/dom/window.rs:use std::fs;
components/script/dom/htmlscriptelement.rs:use std::fs::File;
components/script/dom/userscripts.rs:use std::fs::{File, read_dir};
components/compositing/compositor.rs:use std::fs::File;
components/profile/time.rs:use std::fs::File;
components/profile/heartbeats.rs:use std::fs::File;
components/profile/trace_dump.rs:use std::fs;
components/profile/mem.rs: use std::fs::File;
components/profile/mem.rs: use std::fs::File;
components/gfx/platform/macos/font_template.rs:use std::fs::File;
components/gfx/platform/freetype/android/font_list.rs:use std::fs::File;
components/gfx/platform/freetype/font_template.rs:use std::fs::File;
components/selectors/build.rs:use std::fs::File;
On Tue, Oct 10, 2017 at 11:25 AM, Simon Sapin <simon.sa...@exyr.org> wrote:
> On 10/10/2017 10:34, Paul Rouget wrote:
>>
>> Does it make sense to make it so that Servo does do any disk IO and
>> delegate everything to the embedder?
>>
>> For example, on Android, reading the resources file is hacky because
>> we have to copy the files at startup to the sdcard.
>> Not because we can't have resources files in the apk, but because
>> servo needs a full path, when android provides streams.
>>
>> To solve the resources issue on Android, we could just expose a
>> specific API to read the resource files, but if we agree
>> that Servo should not do any disk IO itself, we would go for a more
>> generic approach.
>
>
> Embedding the resource files in the binary as discussed in
> https://github.com/servo/servo/issues/15635#issuecomment-298699103 should
> solve this, right?
>
> Is there more disk I/O other than that and navigating to a file:// URL?
>
> (By the way, to do we disallow access to file: from http: and other URL
> schemes?)
>
> --
> Simon Sapin
> _______________________________________________
> dev-servo mailing list
> dev-servo@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-servo
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
